public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "speedaemon1 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/15397] New: GDB fails on fork with exec* or posix-spawn*
Date: Thu, 25 Apr 2013 14:11:00 -0000	[thread overview]
Message-ID: <bug-15397-4717@http.sourceware.org/bugzilla/> (raw)

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.


             reply	other threads:[~2013-04-25 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 14:11 speedaemon1 at gmail dot com [this message]
2013-04-25 14:13 ` [Bug c++/15397] " speedaemon1 at gmail dot com
2013-04-25 14:16 ` [Bug gdb/15397] " speedaemon1 at gmail dot com
2013-04-25 14:16 ` speedaemon1 at gmail dot com
2013-04-30 15:19 ` palves at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15397-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).