public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug python/17697] New: MI output is not captured by gdb.command(..., to_string=True)
@ 2014-12-11  6:32 andre.poenitz at digia dot com
  2022-08-12 17:59 ` [Bug python/17697] " tromey at sourceware dot org
  2022-08-12 20:03 ` tromey at sourceware dot org
  0 siblings, 2 replies; 3+ messages in thread
From: andre.poenitz at digia dot com @ 2014-12-11  6:32 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=17697

            Bug ID: 17697
           Summary: MI output is not captured by gdb.command(...,
                    to_string=True)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: andre.poenitz at digia dot com

gdb.command("interpreter -exec mi 'some mi command'", to_string=True) executes
the command, but the output is send to the console, not captured in a string.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug python/17697] MI output is not captured by gdb.command(..., to_string=True)
  2014-12-11  6:32 [Bug python/17697] New: MI output is not captured by gdb.command(..., to_string=True) andre.poenitz at digia dot com
@ 2022-08-12 17:59 ` tromey at sourceware dot org
  2022-08-12 20:03 ` tromey at sourceware dot org
  1 sibling, 0 replies; 3+ messages in thread
From: tromey at sourceware dot org @ 2022-08-12 17:59 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=17697

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I think what happens here is that interpreter-exec calls
interp_set, which calls the interp's resume method.
This method then generally installs a new gdb_stdout (and
other streams), overwriting what gdb.command installed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug python/17697] MI output is not captured by gdb.command(..., to_string=True)
  2014-12-11  6:32 [Bug python/17697] New: MI output is not captured by gdb.command(..., to_string=True) andre.poenitz at digia dot com
  2022-08-12 17:59 ` [Bug python/17697] " tromey at sourceware dot org
@ 2022-08-12 20:03 ` tromey at sourceware dot org
  1 sibling, 0 replies; 3+ messages in thread
From: tromey at sourceware dot org @ 2022-08-12 20:03 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=17697

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
The plan in bug#28948 should fix this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-08-12 20:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-11  6:32 [Bug python/17697] New: MI output is not captured by gdb.command(..., to_string=True) andre.poenitz at digia dot com
2022-08-12 17:59 ` [Bug python/17697] " tromey at sourceware dot org
2022-08-12 20:03 ` tromey at sourceware dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).