delta/glib.git/tests/assert-msg-test.gdb, branch pgriffis/wip/resolver-https gitlab.gnome.org: GNOME/glib.git tests: Work around a gdb bug in assert-msg-test 2017-11-27T11:44:08+00:00 Philip Withnall withnall@endlessm.com 2017-11-27T11:29:15+00:00 82adf7b5da71f44322139f109a3a39455432a961 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 
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
assert-msg-test: Explicitly quit gdb session to avoid zombie 2014-06-10T12:57:54+00:00 Daniel Macks dmacks@netspace.org 2014-06-10T10:00:33+00:00 93d0c632326064f3e72f0e88e3dc971bdfc74af0 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 
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
Fix the assert-msg test 2013-01-14T22:35:47+00:00 Matthias Clasen mclasen@redhat.com 2013-01-14T22:21:52+00:00 d1c25d3191214ce6cd289f0756e6027c35cc2075 gdb is playing games with us, by breaking -x /dev/stdin 
gdb is playing games with us, by breaking -x /dev/stdin