OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Use mi_create_floating_varobj 

In gdb.python/py-mi.exp, two varobjs container and nscont are created
when pretty-printing is still not enabled, so they are not dynamic
varobj, IIUC.  In this patch, we use mi_create_floating_varobj instead
of mi_create_dynamic_varobj.

gdb/testsuite:

2013-11-22  Yao Qi  <yao@codesourcery.com>

	* gdb.python/py-mi.exp: Use mi_create_floating_varobj instead
	of mi_create_dynamic_varobj.
This commit is contained in:
Yao Qi 2013-11-10 10:30:46 +08:00
parent 46b2ff5b53
commit 0061ea2440
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,8 @@
2013-11-22 Yao Qi <yao@codesourcery.com>
* gdb.python/py-mi.exp: Use mi_create_floating_varobj instead
of mi_create_dynamic_varobj.
2013-11-20 Pedro Alves <palves@redhat.com>
* gdb.base/maint.exp (maint print objfiles): Consume one line at a

4
gdb/testsuite/gdb.python/py-mi.exp
View File

@ -49,7 +49,7 @@ mi_gdb_test "python exec (open ('${remote_python_file}').read ())" ""
mi_continue_to_line [gdb_get_line_number {MI breakpoint here} ${srcfile}] \
"step to breakpoint"
mi_create_dynamic_varobj container c \
mi_create_floating_varobj container c \
"create container varobj, no pretty-printing"
mi_list_varobj_children container {
@ -60,7 +60,7 @@ mi_list_varobj_children container {
mi_delete_varobj container "delete varobj"
mi_create_dynamic_varobj nscont nstype \
mi_create_floating_varobj nscont nstype \
"create nscont varobj, no pretty-printing"
mi_list_varobj_children nscont {