[Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Brian Murray]

It's also worth noting that running strings on the core file does reveal
the contents of the assertion message.

$ strings core
....
CORE
main: assertion 1 < 0): (1 < 0)
sertion failed (
LINUX
main: assertion 1 < 0): (1 < 0)
....

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  New
Status in gdb package in Ubuntu:
  New

Bug description:
  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR:<stdin>:2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg 
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg 
  $2 = 0x4f6dbdc0 <error: Cannot access memory at address 0x4f6dbdc0>

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions