glib/tests/assert-msg-test.gdb

run
set print elements 0
# Work around https://sourceware.org/bugzilla/show_bug.cgi?id=22501
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`
tests: Work around a gdb bug in assert-msg-test It seems that when GLib is compiled without CFLAGS=-g, gdb can’t work out the size of __glib_assert_msg, so assumes it’s 4 bytes — even on 64-bit systems. This causes it to not read the most significant 4 bytes of the assertion message pointer, and hence it can’t print the stored assertion message. This causes assert-msg-test to fail. The upstream gdb bug is https://sourceware.org/bugzilla/show_bug.cgi?id=22501. Work around that by referencing and dereferencing __glib_assert_msg so that gdb treats it as a pointer of sizeof(char*) rather than of the size it incorrectly calculated from the library’s symbol table (or through some other mystical process). Signed-off-by: Philip Withnall <withnall@endlessm.com> https://bugzilla.gnome.org/show_bug.cgi?id=782057 2017-11-27 12:29:15 +01:00			`# Work around https://sourceware.org/bugzilla/show_bug.cgi?id=22501`
			`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`