** Description changed: + [Impact] + apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. + + [Test Case] + Run the autopkgtest and observe the failure. + With the version of the package in proposed the test will not be run. + + [Regression Potential] + We are just disabling a broken test so there is none. + 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 + (gdb) print __glib_assert_msg $1 = 1332592064 - (gdb) print (char*) __glib_assert_msg + (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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689344 Title: print of __glib_assert_msg not returning a message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
