From: Kevin Pouget <kevin.pouget@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch] [python] python/12686
Date: Wed, 20 Apr 2011 20:10:00 -0000 [thread overview]
Message-ID: <BANLkTimwFH_j-07a4HKewdL37a80EXup_w@mail.gmail.com> (raw)
In-Reply-To: <m3aafk1zxn.fsf@fleche.redhat.com>
> TBH I think asking the user questions here is weird.
I'm not sure about the right way to do, I haven't had time to consider
your suggestion on the main mailing list, but if you consider the
situation where you want to ask the user (from Python) if s/he wants
to stop the inferior.
Currently, one way would be to do it here, the other would be in the
"stop" event handler, with `gdb.execute("continue")', but I don't
really like this solution, being under a Python callstack during the
execution seems a bit strange, doesn't it ?
Cordially,
Kevin
next prev parent reply other threads:[~2011-04-20 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 13:50 Phil Muldoon
2011-04-20 19:32 ` Tom Tromey
2011-04-20 20:10 ` Kevin Pouget [this message]
2011-04-25 19:29 ` Tom Tromey
2011-04-28 13:40 ` Kevin Pouget
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=BANLkTimwFH_j-07a4HKewdL37a80EXup_w@mail.gmail.com \
--to=kevin.pouget@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=tromey@redhat.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