X-Debbugs-CC: zu...@debian.org, g...@debian.org
We are trying to track down the source of a program termination under
the debugger due to a SIGILL. The program does not perform feature
probing, so we don't believe its coming from the program.
If the program is run outside the debugger everything is fine. If the
program is run inside the debugger without a breakpoint everything is
fine. However, if the program has a breakpoint added, it eventually
crashes due to a SIGILL.
We don't rule out a program bug on our part. However, stable code is
now producing the issue, too. In the past when I added the code and
debugged it, the issue did not surface.
A question was asked on Stack Overflow:
https://stackoverflow.com/q/45649778/608639. In the comments, this bug
report was discussed:
Start reading the 10833 bug around Comment 8. Comment 11 and Comment
12 are definitely what we are experiencing.
Comment 15 says its fixed after a 2.6 kernel, but I am experiencing it
under 3.4.113-bananian and 4.1.15-ti-rt-r40-beaglebone kernels.
Thanks in advance.
$ apt-cache show gdb
Maintainer: Héctor Orón Martínez <zu...@debian.org>
Depends: libc6 (>= 2.15), libexpat1 (>= 2.0.1), liblzma5 (>=
5.1.1alpha+20110809), libncurses5 (>= 5.5-5~), libpython2.7 (>= 2.7),
libreadline6 (>= 6.0), libtinfo5, zlib1g (>= 1:1.2.0)
Recommends: libc-dbg, gdbserver
Description-en: GNU Debugger
GDB is a source-level debugger, capable of breaking programs at