gdb

internal-error: unknown ptrace event 5

Bug #172311 reported by gst
2
Affects Status Importance Assigned to Milestone
gdb
New
Undecided
Unassigned
gdb (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gdb

This problem occured while I tried to debug a possible GCC problem. For some reason GDB receives an unknown ptrace event as soon as GCC crashes.

The problem seems to be the same as reported in this report (from 2005):
http://sourceware.org/ml/gdb/2005-05/msg00368.html

It seems that this problem is reproducable in 100% of the cases (at least on my machine).

The file foo.c used below (to crash GCC) is available at:
http://virtual.sysfrog.org/~gst/gccbug/foo.c

gst@pico:~$ gdb -q gcc
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) set follow-fork-mode child
(gdb) run -Wall -pedantic foo.c
Starting program: /usr/bin/gcc -Wall -pedantic foo.c
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
/build/buildd/gdb-6.6.dfsg/gdb/linux-nat.c:578: internal-error: unknown ptrace event 5
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
/build/buildd/gdb-6.6.dfsg/gdb/linux-nat.c:578: internal-error: unknown ptrace event 5
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted

Revision history for this message
gst (gstarnberger) wrote :
Matthias Klose (doko)
Changed in gdb:
status: New → Triaged
Revision history for this message
Matthias Klose (doko) wrote :

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel free to re-open the issue if the problem persists.

Changed in gdb (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.