From: Andrey Utkin <autkin@undo.io>
To: gdb@sourceware.org
Subject: gdb.execute(to_string=True) doesn't capture signal notice anymore
Date: Wed, 15 Aug 2018 20:09:00 -0000 [thread overview]
Message-ID: <20180815200855.GA24829@undo-autkin> (raw)
Hi,
We have some code which uses the fact of GDB 7.7 behaviour that if you
execute python code like
s = gdb.execute("run", to_string=True)
and, say, debuggee generates SIGTRAP, then result `s` includes the
string "Program received signal SIGTRAP, Trace/breakpoint trap."
What we see is that since 7.12.1 or earlier, and until now, this is no
longer the case - this message is not captured but is only printed to
terminal.
Before I dig into "fixing it", I want to know maintainers opinion - is
the current behaviour exactly what you like, or it's an unintended
regression and you'd prefer to preserve the old way?
next reply other threads:[~2018-08-15 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 20:09 Andrey Utkin [this message]
2018-08-16 14:35 ` Phil Muldoon
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=20180815200855.GA24829@undo-autkin \
--to=autkin@undo.io \
--cc=gdb@sourceware.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