I was trying to investigate a failed retrace on armhf and received the following when running apport-retrace with -g.
Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
-utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' --ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
helper"' --ex 'core-file /tmp/apport_core_36z3Va'
GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
Copyright (C) 2014 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 "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://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".
The target architecture is assumed to be arm
Reading symbols from /tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols from /tmp/apport-utopic/usr/lib/debug/.bu
ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
done.
BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size >= 19316736, found: 9502720.
[New LWP 15327]
[New LWP 15530]
[New LWP 15321]
Cannot access memory at address 0xb6fa7948
Cannot access memory at address 0xb6fa7944
When running apport-retrace with -o, a new crash file is created with a broken Stacktrace. This makes sense given that the core file is corrupt. I think apport-retrace should do something different here, maybe write a RetraceFailure key to the report, not write the report at all, or just exit with an error regarding the core file size difference.
I was trying to investigate a failed retrace on armhf and received the following when running apport-retrace with -g.
Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set gnutarget elf32-littlearm' --ex 'set debug-file- directory /tmp/apport usr/lib/ debug' --ex 'set solib-absolute- prefix /tmp/apport-utopic' --ex 'file "/tmp/apport- utopic/ /usr/lib/ ubuntu- push-client/ signing- core_36z3Va' gnu.org/ licenses/ gpl.html> www.gnu. org/software/ gdb/bugs/>. www.gnu. org/software/ gdb/documentati on/>. utopic/ /usr/lib/ ubuntu- push-client/ signing- helper. ..Reading symbols from /tmp/apport- utopic/ usr/lib/ debug/. bu 0d/28e75c6b9149 132f8940077618a 904989a75ed. debug.. .done. core_36z3Va is truncated: expected core file size >= 19316736, found: 9502720.
-utopic/
helper"' --ex 'core-file /tmp/apport_
GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://
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 "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://
Find the GDB manual and other documentation resources online at:
<http://
For help, type "help".
Type "apropos word" to search for commands related to "word".
The target architecture is assumed to be arm
Reading symbols from /tmp/apport-
ild-id/
done.
BFD: Warning: /tmp/apport_
[New LWP 15327]
[New LWP 15530]
[New LWP 15321]
Cannot access memory at address 0xb6fa7948
Cannot access memory at address 0xb6fa7944
When running apport-retrace with -o, a new crash file is created with a broken Stacktrace. This makes sense given that the core file is corrupt. I think apport-retrace should do something different here, maybe write a RetraceFailure key to the report, not write the report at all, or just exit with an error regarding the core file size difference.