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

[Brian Murray]

This was not failing in the autopkgtest for yakkety but does now in a
chroot.

(yakkety-amd64)root at impulse:/home/bdmurray/source-trees/apport/glib-assert-test# ./glib-assert.sh 
**
ERROR:<stdin>:2:main: assertion failed (1 < 0): (1 < 0)
Aborted (core dumped)

warning: core file may not match specified executable file.
[New LWP 15613]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./glib_assertion.bin'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
58      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
$1 = 0x19545dc0 <error: Cannot access memory at address 0x19545dc0>

-- 
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