Apport self test FAIL: add_gdb_info() with SIGABRT/assert()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
Triaged
|
Low
|
Unassigned |
Bug Description
Reproduce using:
$ ./test/run
+ python -tt /usr/lib/
add_gdb_info() with core dump file reference. ... ok
add_gdb_info() with SIGABRT/assert() ... readelf: Error: core: Failed to read file's magic number
FAIL
add_gdb_info() with inline core dump. ... ok
add_gdb_info() with a script. ... readelf: Error: /tmp/core: Failed to read file's magic number
FAIL
add_hooks_info(). ... ok
add_os_info(). ... ok
add_package_info(). ... ok
classification of $PATH. ... ok
add_proc_info(). ... ok
add_user_info(). ... ok
methods get along with binary data. ... ok
check_ignored() for system-wise blacklist. ... ok
_check_
crash_signature(). ... ok
_gen_stacktrace
has_useful_
mark_ignore() and check_ignored(). ... ok
obsolete_
search_
standard_title(). ... ok
=======
FAIL: add_gdb_info() with SIGABRT/assert()
-------
Traceback (most recent call last):
File "/usr/lib/
stdout=
AssertionError
=======
FAIL: add_gdb_info() with a script.
-------
Traceback (most recent call last):
File "/usr/lib/
stdout=
AssertionError
-------
Ran 20 tests in 6.723s
FAILED (failures=2)
Sometimes I get thisk, too, seems to be a race condition. In 9 cases out of 10 I don't get it, though. Is this constantly reproducible for you?