I tested the yakkety core file and binary with a xenial version of gdb and didn't still received the cannot access memory error, so I don't think its a gdb bug.
** Package changed: gdb (Ubuntu) => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Released Status in glib2.0 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
