This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/21506] python execute(to_string=True) no longer captures certain output since e7ea3ec7
- From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 03 Sep 2017 18:51:06 +0000
- Subject: [Bug gdb/21506] python execute(to_string=True) no longer captures certain output since e7ea3ec7
- Auto-submitted: auto-generated
- References: <bug-21506-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21506
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-09-03
CC| |tromey at sourceware dot org
Ever confirmed|0 |1
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I've also noticed this when using my python gdb gui --
the gui uses to_string=True for some commands to suppress output,
but gdb still emits the output anyway now.
For example in my case it happens in tui_on_normal_stop, which
calls print_stop_event for each UI.
I'm not sure what can be done about this. if nothing, it's worth
noting that the output is sub-par as well:
(top) 30 args.argv = argv;
31 args.interpreter_p = INTERP_CONSOLE;
... that is, it doesn't try to erase the prompt first.
--
You are receiving this mail because:
You are on the CC list for the bug.