glib/tests/assert-msg-test.gdb

run
set print elements 0
print (char*) __glib_assert_msg
quit
Fix the assert-msg test gdb is playing games with us, by breaking -x /dev/stdin 2013-01-14 23:21:52 +01:00			`run`
			`set print elements 0`
			`print (char*) __glib_assert_msg`
assert-msg-test: Explicitly quit gdb session to avoid zombie gdb is run in batch mode, and can leave leave the program being executed/debugged running when the batchfile is finished. Explicitly "quit"ing the subprocess prevents it from leaving the stray subprocess when gdb finishes. https://bugzilla.gnome.org/show_bug.cgi?id=731366 2014-06-10 12:00:33 +02:00			`quit`