This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/15397] New: GDB fails on fork with exec* or posix-spawn*
- From: "speedaemon1 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 25 Apr 2013 14:11:45 +0000
- Subject: [Bug c++/15397] New: GDB fails on fork with exec* or posix-spawn*
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15397
Bug #: 15397
Summary: GDB fails on fork with exec* or posix-spawn*
Product: gdb
Version: 7.3
Status: NEW
Severity: critical
Priority: P2
Component: c++
AssignedTo: unassigned@sourceware.org
ReportedBy: speedaemon1@gmail.com
Classification: Unclassified
Created attachment 6997
--> http://sourceware.org/bugzilla/attachment.cgi?id=6997
GDB Trace of execution using posix_spawn()
When attempting to debug a application in C++ that implements fork() to execute
another process through either exec* or posix_spawn* GDB fails.
132,000 ~"/home/dkg/src/gdb/gdb-7.3/gdb/thread.c:620: internal-error:
is_thread_state: Assertion `tp\' failed.\nA problem internal to GDB has been
detected,\nfurther debugging may prove unreliable.\nQu\ it this debugging
session? "
Using fork() alone executes correctly. Only when using exec* or posix_spawn*
generates the issue.
Attempting this on the following platform
OS: Debian Squeeze (Linux 2.6.32-5-amd64)
GDB version 7.3 (Debian Backport)
I am using Eclipse CDT IDE to interact with GDB and attached is the GDB Trace.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.