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

[Brian Murray]

Verification for yakkety:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
yakkety/yakkety/amd64/a/apport/20170512_193229_92825@/log.gz

Verification for zesty:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/a/apport/20170512_193953_7d1ed@/log.gz

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glib2.0 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
Status in apport source package in Yakkety:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [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
  $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