Bug 1629408

Summary: Backtrace generation for crashes always fails: UI shows "Frame start sequence expected.", backtrace file "A syntax error in expression, near `full'."
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 29CC: abrt-devel-list, bugzilla, jakub, jmilan, mhabrnal, michal.toman, mkutlak, mmarusak
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: abrt-2.10.10-5.fc29 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-21 05:34:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Williamson 2018-09-15 21:40:11 UTC 
Every time I attempt to report a crash in Fedora 29 or Rawhide - well, first retrace server generation fails, that's https://github.com/abrt/retrace-server/issues/220 . Then, when I try and generate a backtrace locally, it always fails. If using gnome-abrt, it says the backtrace is unusable. If using report-cli, I get this:

Generating backtrace
Backtrace is generated and saved, 35591 bytes
Backtrace parsing failed for .
180:0: Frame start sequence expected.

Looking at the backtrace file itself, I see this:

...
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7f5703fff700 (LWP 26025))]

Thread 1 (Thread 0x7f5703fff700 (LWP 26025)):
A syntax error in expression, near `full'.
From                To                  Syms Read   Shared Object Library
0x00007f571ff91950  0x00007f571ff94e9d  Yes         /lib64/libnautilus-extension.so.1
0x00007f571fe8adc0  0x00007f571ff08732  Yes         /lib64/libglib-2.0.so.0
0x00007f571f7b7e90  0x00007f571fb0e98b  Yes (*)     /lib64/libgtk-3.so.0
...

i.e. the entire actual frame sequence is missing, apparently due to some sort of 'syntax error'.

Note I can always generate backtraces for the same crashes OK using 'coredumpctl gdb (pid)', so systemd-coredump doesn't have the same problem.
Comment 1 Adam Williamson 2018-09-15 21:47:01 UTC 
https://github.com/abrt/satyr/commit/91e3bc23a654e3daf1bf6546b06b9de7d00dbd59 looks interesting, but that's a commit to a *test*...
Comment 2 Adam Williamson 2018-09-15 21:51:39 UTC 
aha:

https://github.com/abrt/abrt/commit/057f8b0395a37765b856737cb25186c52b300389

now to figure out if that *broke* it, or if that *fixes* it but it's not in Fedora yet.
Comment 3 Fedora Update System 2018-09-15 22:29:07 UTC 
abrt-2.10.10-5.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c5dd4f97dc
Comment 4 Fedora Update System 2018-09-17 01:07:25 UTC 
abrt-2.10.10-5.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c5dd4f97dc
Comment 5 Fedora Update System 2018-09-21 05:34:52 UTC 
abrt-2.10.10-5.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
Comment 6 Adam Williamson 2018-09-24 22:37:04 UTC 
Dropping CommonBugs as this is fixed.