This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested in
Frederic, any news on this? Is this still an issue for you?
--
kernel generates spurious SIGTRAPs in debugged applications
https://bugs.launchpad.net/bugs/253591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
I'll test as soon as I install the final Intrepid on one of my boxes.
However I'm quite disappointed about the way this bug is handled. It's a
serious bug that most users will attribute to GDB being unable to debug
C++ code. I've seen at least one user asking about it on the GDB
development mailin
The Intrepid Ibex 8.10 Beta release was most recently announced -
http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27
Ubuntu kernel. It would be great if you could test and verify if this
is still an issue. The status is being set to Incomplete until we
receive further feedback.
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Something wasn't very clear in what I said above. This isn't only some
bizarre testsuite FAIL. This affects real life debugging. I can't debug
my C++ code at all due to this bug. The bug manifests itself with some
sequences of stepping and calling debuggee functions. It does it all the
time when I
