public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/15397] GDB fails on fork with exec* or posix-spawn*
Date: Tue, 30 Apr 2013 15:19:00 -0000	[thread overview]
Message-ID: <bug-15397-4717-6Kl9Vyp51o@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15397-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15397

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |palves at redhat dot com
         Resolution|                            |WORKSFORME

--- Comment #2 from Pedro Alves <palves at redhat dot com> 2013-04-30 15:19:51 UTC ---
Please try a more recent GDB; we've just released 7.6.

That said, I've tried it myself, on the command line, with:

$ gdb -i=mi pr6998 -ex "set target-async on" -ex "set non-stop on" -ex "set
detach-on-fork off"

both mainline and 7.6, and I saw no crash.

Please reopen if you can reproduce this with 7.6 or mainline.

Thanks.

-- 
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.


      parent reply	other threads:[~2013-04-30 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 14:11 [Bug c++/15397] New: " speedaemon1 at gmail dot com
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 [this message]

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-6Kl9Vyp51o@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).