public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/13728] New: GDB crashes on catch exec -> detach
Date: Thu, 23 Feb 2012 10:18:00 -0000 [thread overview]
Message-ID: <bug-13728-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13728
Bug #: 13728
Summary: GDB crashes on catch exec -> detach
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: cli
AssignedTo: unassigned@sourceware.org
ReportedBy: jan.kratochvil@redhat.com
Classification: Unclassified
#include <unistd.h>
#include <assert.h>
#include <stdio.h>
int
main (void)
{
for (;;)
{
int i;
sleep (5);
puts ("fork");
i = fork ();
assert (i >= 0);
if (i == 0)
{
sleep (1);
execlp ("sh", "sh", "-c", "echo x;sleep 60", NULL);
assert (0);
}
}
}
gdb ~/t/forkdetach -ex 'set detach-on-fork off' -ex 'set non-stop on' -ex 'set
target-async on'
(gdb) catch exec
Catchpoint 1 (exec)
(gdb) commands 1
Type commands for breakpoint(s) 1, one per line.
End with a line saying just "end".
>detach
>end
(gdb) r &
[New process 12872]
process 12872 is executing new program: /bin/bash
Catchpoint 1 (exec'd /bin/bash), 0x00000032a76016e0 in _start () from
/lib64/ld-linux-x86-64.so.2
warning: x
Segmentation fault
gdb-7.3.50.20110722-10.fc16.x86_64
--
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.
next reply other threads:[~2012-02-23 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 10:18 jan.kratochvil at redhat dot com [this message]
2012-02-29 17:02 ` [Bug cli/13728] " tromey at redhat dot com
2012-02-29 21:43 ` tromey at redhat dot com
2012-03-14 15:20 ` palves at redhat dot com
2024-01-09 19:53 ` ssbssa at sourceware dot org
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-13728-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).