This bug was fixed in the package apport - 2.20.3-0ubuntu8.3
---------------
apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium
* Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)
* Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
* data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)
-- Brian Murray <br...@ubuntu.com> Wed, 10 May 2017 18:10:32 -0700
** Changed in: apport (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport 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 Released
Status in glib2.0 source package in Yakkety:
New
Status in apport source package in Zesty:
Fix Released
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
--
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
