Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Relationship between GDB commands in Python and Guile
Date: Tue, 17 Mar 2015 13:44:00 -0000	[thread overview]
Message-ID: <878uevbux7.fsf@igalia.com> (raw)
In-Reply-To: <86fv93g79l.fsf@gmail.com> (Yao Qi's message of "Tue, 17 Mar 2015	12:04:06 +0000")

Hi,

Quick answer:

On Tue 17 Mar 2015 13:04, Yao Qi <qiyaoltc@gmail.com> writes:

> Andy Wingo <wingo@igalia.com> 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.

Andy


  reply	other threads:[~2015-03-17 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 13:44 Andy Wingo
2015-02-27  4:21 ` Doug Evans
2015-03-16 12:48   ` Pedro Alves
2015-03-17 12:04 ` Yao Qi
2015-03-17 13:44   ` Andy Wingo [this message]
2015-03-17 15:50 ` Doug Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878uevbux7.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox