Why: sp-rich-core "/var/cache/core-dumps/ofonod-xqbt52-11-14640/coredump" is not a core dump: file format not recognized

Platform Development
1

X10III: I got jolla-settings-crash-reporter installed and successfully captured a rich core archive of ofonod and connmand immediately crash, after App Support lost mobile data again, and I tested flipping “Mobile data” in Android Settings.

Then I discovered sp-rich-core-postproc and used rich-core-extract to extract the rcore archive.

Now I’m trying to gdb a backtrace out of it, but running into topic problem.

[defaultuser@Xperia10III core-dumps]$ gdb -ex "set verbose on" /usr/sbin/ofonod ofonod-xqbt52-11-14640/coredump 
GNU gdb (GDB) Mer (12.1.0+git2)
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-meego-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/ofonod...
Reading symbols from /usr/lib/debug/usr/sbin/ofonod-1.29+git11-1.15.2.jolla.aarch64.debug...
"/var/cache/core-dumps/ofonod-xqbt52-11-14640/coredump" is not a core dump: file format not recognized
(gdb)

OTOH file identifies it as a legit coredump?

[defaultuser@Xperia10III core-dumps]$ file ofonod-xqbt52-11-14640/coredump 
ofonod-xqbt52-11-14640/coredump: ELF 64-bit LSB core file, ARM aarch64, version 1 (SYSV), SVR4-style, from '/usr/sbin/ofonod -n --nobacktrace --noplugin=,he910,dun_gw_bluez5,hfp_bluez5,cd', real uid: 0, effective uid: 0, real gid: 0, effe
ctive gid: 0, bad note name size 0xf1a353c0, bad note name size 0xf1b3d000, bad note name size 0xf1f12000

What can I try next? Internet had no further ideas.

2

What exactly is the error gdb gives you?
You will also need debug info files, else the stacktrace will be very obscure.

1 Like
3

I added full terminal output, not sure how I forgot it :+1:

Yes, all debuginfo and -source are installed for relevant packages.

(PS I’ve been gdb-ing successfully on amd64 for years. Never seen “not a core dump” problem before.)

EDIT I also have an rcore archive for connmand crash, exact same problem. Is it some kind of a systemic issue with sp-rich-core?

4

Definitely not an expert; but the “bad note” parts of filedont look promising. Is the coredump you use in gdb postprocessed by any of the two utilites you mentioned? If yes, have you tried the vanilla coredump?