This is the mail archive of the
mailing list for the GDB project.
Re: Relationship between GDB commands in Python and Guile
- From: Andy Wingo <wingo at igalia dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 17 Mar 2015 14:44:20 +0100
- Subject: Re: Relationship between GDB commands in Python and Guile
- Authentication-results: sourceware.org; auth=none
- References: <87bnkgoki0 dot fsf at igalia dot com> <86fv93g79l dot fsf at gmail dot com>
On Tue 17 Mar 2015 13:04, Yao Qi <email@example.com> writes:
> Andy Wingo <firstname.lastname@example.org> writes:
>> An open question would be how to indicate that python extensions win
>> over guile extensions. Perhaps we should query extensions by language,
>> then, and then list python ones first. Having a unified "priority"
>> doesn't make sense in that context. Perhaps the pretty-printing (etc)
>> mechanism should, in that case, instead be more fine-grained -- not just
>> "try python first", but instead trying the printers (frame filters, etc)
>> in order of priority. Perhaps that's too much setup work though; not
>> sure what the cost is to "enter" python mode etc.
> I'd like to know why is such question raised? In practise, is it common
> that users install two pretty-printers, one is python and one is guile?
Imagine a program that uses two libraries, one of which has a
libfoo-gdb.py file installed, and the other that has libbar-gdb.scm
installed. Then you could have pretty printers, frame filters,
unwinders, etc defined for each library but in different languages.