print of __glib_assert_msg not returning a message

Bug #1689344 reported by Brian Murray
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Undecided
Unassigned
Yakkety
Fix Released
Undecided
Brian Murray
Zesty
Fix Released
Undecided
Brian Murray
glib2.0 (Ubuntu)
New
Undecided
Unassigned
Yakkety
New
Undecided
Unassigned
Zesty
New
Undecided
Unassigned

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.

Revision history for this message
Brian Murray (brian-murray) wrote :

There is another apport test, "test_add_gdb_info_abort_libnih", which was disabled for similar reasons - e.g. "Cannot access memory".

https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1580601

Revision history for this message
Brian Murray (brian-murray) wrote :

It's also worth noting that running strings on the core file does reveal the contents of the assertion message.

$ strings core
....
CORE
main: assertion 1 < 0): (1 < 0)
sertion failed (
LINUX
main: assertion 1 < 0): (1 < 0)
....

Revision history for this message
Brian Murray (brian-murray) wrote :

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

(yakkety-amd64)root@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@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>

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apport - 2.20.4-0ubuntu6

---------------
apport (2.20.4-0ubuntu6) artful; urgency=medium

   * Disable report.test_add_gdb_info_abort_glib test case for now, as the
     glib assertion message is broken under current Ubuntu (LP: #1689344)
  * etc/apport/crashdb.conf: Enable Launchpad crash reports for artful.

 -- Brian Murray <email address hidden> Mon, 08 May 2017 11:10:34 -0700

Changed in apport (Ubuntu):
status: New → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

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.

affects: gdb (Ubuntu) → glib2.0 (Ubuntu)
Changed in apport (Ubuntu Yakkety):
status: New → In Progress
assignee: nobody → Brian Murray (brian-murray)
Changed in apport (Ubuntu Zesty):
status: New → In Progress
assignee: nobody → Brian Murray (brian-murray)
description: updated
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Brian, or anyone else affected,

Accepted apport into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in apport (Ubuntu Zesty):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Brian, or anyone else affected,

Accepted apport into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in apport (Ubuntu Yakkety):
status: In Progress → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apport - 2.20.4-0ubuntu4.1

---------------
apport (2.20.4-0ubuntu4.1) zesty; urgency=medium

  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
    glib assertion message is broken under current Ubuntu (LP: #1689344)
  * 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)

 -- Brian Murray <email address hidden> Wed, 10 May 2017 17:05:11 -0700

Changed in apport (Ubuntu Zesty):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for apport has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Wed, 10 May 2017 18:10:32 -0700

Changed in apport (Ubuntu Yakkety):
status: Fix Committed → Fix Released
nassim (moujane)
Changed in glib2.0 (Ubuntu):
assignee: nobody → nassim (moujane)
Changed in glib2.0 (Ubuntu):
assignee: nassim (moujane) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.