print of __glib_assert_msg not returning a message
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_
[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_
With the generated binary, it used to return the following:
$2 = 0x7fadc0 "ERROR:
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.
Related branches
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 |
Changed in glib2.0 (Ubuntu): | |
assignee: | nobody → nassim (moujane) |
Changed in glib2.0 (Ubuntu): | |
assignee: | nassim (moujane) → nobody |
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