python: Use console format for output of gdb.execute command
authorCatalin Udma <catalin.udma@freescale.com>
Mon, 29 Feb 2016 14:16:19 +0000 (16:16 +0200)
committerCatalin Udma <catalin.udma@freescale.com>
Thu, 31 Mar 2016 12:32:38 +0000 (15:32 +0300)
commite7ea3ec7c623be0b9be1eaf4929794652a84be11
tree4b8fca9e668f79d3e4239c1204a61672b5c11fb7
parentf7c382926d78b2d6d96b02275e6e16797b132d71
python: Use console format for output of gdb.execute command

When gdb is started in MI mode, the output of gdb.execute
command is in MI-format in case when it is executed from python stop
handler while for all other cases the output is in console-format.

To assure consistent output format, this is fixed by using the console
format for all python gdb command executions.

PR python/19743

gdb/ChangeLog:
2016-03-31  Catalin Udma  <catalin.udma@freescale.com>

PR python/19743
* python/python.c (execute_gdb_command): Use console uiout
when executing gdb command.
* utils.c (restore_ui_out_closure): New structure.
(do_restore_ui_out): New function.
(make_cleanup_restore_ui_out): Likewise.
* utils.h (make_cleanup_restore_ui_out): Declare.

gdb/testsuite/ChangeLog:
2016-03-31  Catalin Udma  <catalin.udma@freescale.com>

PR python/19743
* gdb.python/py-mi-events-gdb.py: New file.
* gdb.python/py-mi-events.c: New file.
* gdb.python/py-mi-events.exp: New file.

Signed-off-by: Catalin Udma <catalin.udma@freescale.com>
gdb/ChangeLog
gdb/python/python.c
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.python/py-mi-events-gdb.py [new file with mode: 0644]
gdb/testsuite/gdb.python/py-mi-events.c [new file with mode: 0644]
gdb/testsuite/gdb.python/py-mi-events.exp [new file with mode: 0644]
gdb/utils.c
gdb/utils.h