[Aptitude-devel] Bug#832710: aptitude: segfault in arm* qemu environments
Gianfranco Costamagna
locutusofborg at debian.org
Thu Jul 28 09:56:04 UTC 2016
Source: aptitude
Version: 0.8.2-1
Severity: normal
Hi, since some months, the default pbuilder installation (the default uses aptitude resolver) crashes
when under a qemu environment.
steps to reproduce
pbuilder-dist sid arm64 create
pbuilder-dist sid arm64 update
crash.
I tried to gdb but I didn't have to much luck in having a backtrace
gdb aptitude
qemu: Unsupported syscall: 278
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 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-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"...
Reading symbols from aptitude...Reading symbols from /usr/lib/debug/.build-id/ea/60762dcca33c7f2150747763c0c39174939862.debug...r update
done.
done.
(gdb) r update
Starting program: /usr/bin/aptitude update
qemu: Unsupported syscall: 117
During startup program terminated with signal SIGSEGV, Segmentation fault.
(gdb)
(gdb)
(gdb) bt
No stack.
(gdb) bt all
No stack.
(gdb) quit
also strace seems to have some issues here
qemu: Unsupported syscall: 117
qemu: Unsupported syscall: 117
/usr/bin/strace: ptrace(PTRACE_TRACEME, ...): Function not implemented
+++ exited with 1 +++
you can find some bits in the discussion below
https://lists.debian.org/debian-mentors/2016/07/msg00644.html
probably this is a bug in qemu itself, but I thought it was better to report it here,
to make you aware of the issue.
Switching to apt resolver or another one "fixes" the issue.
as usual, feel free to reassign or give me some pointers to debug further the issue
thanks a lot,
Gianfranco
More information about the Aptitude-devel
mailing list