From: Kevin Pouget <kevin.pouget@gmail.com>
To: pmuldoon@redhat.com, Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb@sourceware.org
Subject: Re: [Python] Input from user from extended breakpoint `stop' function
Date: Wed, 20 Apr 2011 07:36:00 -0000 [thread overview]
Message-ID: <BANLkTi=-t7XocAbzFdcSvbeoKLVreH+rEw@mail.gmail.com> (raw)
In-Reply-To: <m38vv6c4l6.fsf@redhat.com>
>> Any solution, or shall I send a bug report?
> Bug report please.
http://sourceware.org/bugzilla/show_bug.cgi?id=12686 (what does PR mean ?)
>> The terminal still belongs to the inferior. Before gdb is doing any
>> input it must call terminal_ours.
that's interesting, but why `print' functions work correctly, without
sending any SIGTTOU
> Thanks, that is good info. I did not know that. I wonder if we should
> call that before handing over control to the python executed script in
> the breakpoint "stop" callback? Or maybe provide a Python API call to
> turn control of the TTY to GDB and likewise to the inferior.
>
> Any opinions on this would be great. What do you (all) think?
I would prefer a python-transparent handling, ie `terminal_ours'
called before giving the hand to the Python callback, to hide GDB's
complexity from the script interface (I guess there won't be so many
situations where this case occurs?).
However if `terminal_ours' is very costly (in comparison to the
breakpoint itself), it might not be very wise ...
Cordially,
Kevin
next prev parent reply other threads:[~2011-04-20 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 14:42 Kevin Pouget
2011-04-19 20:10 ` Phil Muldoon
2011-04-19 20:44 ` Andreas Schwab
2011-04-19 21:30 ` Phil Muldoon
2011-04-20 7:36 ` Kevin Pouget [this message]
2011-04-20 7:48 ` Andreas Schwab
2011-04-21 11:38 ` Kevin Pouget
2011-04-20 15:41 ` Tom Tromey
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='BANLkTi=-t7XocAbzFdcSvbeoKLVreH+rEw@mail.gmail.com' \
--to=kevin.pouget@gmail.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=schwab@linux-m68k.org \
/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