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 gdb/17347] New: Regression: GDB stopped on run with attached process Date: Wed, 03 Sep 2014 07:43:00 -0000 [thread overview] Message-ID: <bug-17347-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17347 Bug ID: 17347 Summary: Regression: GDB stopped on run with attached process Product: gdb Version: 7.8 Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com CC: palves at redhat dot com Host: x86_64-linux-gnu Target: x86_64-linux-gnu sleep 1h&p=$!;sleep 0.1;gdb -batch sleep $p -ex r PASS: [2] 22970 0x0000003fdf8bc780 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:81 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) /usr/bin/sleep: missing operand Try '/usr/bin/sleep --help' for more information. [Inferior 1 (process 23030) exited with code 01] [2]+ Killed sleep 1h FAIL: [2] Killed sleep 1h [3]+ Stopped ./gdb/gdb -batch sleep $! -ex r 7180e04a36d812bbea2c280f2db33a7e8ce6b07b is the first bad commit commit 7180e04a36d812bbea2c280f2db33a7e8ce6b07b Author: Pedro Alves <palves@redhat.com> Date: Wed Jul 9 15:59:02 2014 +0100 Fix "attach" command vs user input race private Red Hat reference: https://bugzilla.redhat.com/show_bug.cgi?id=1136704 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-09-03 7:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-03 7:43 jan.kratochvil at redhat dot com [this message] 2014-09-03 9:58 ` [Bug gdb/17347] " palves at redhat dot com 2014-09-03 9:59 ` palves at redhat dot com 2014-09-03 20:12 ` palves at redhat dot com 2014-09-11 12:14 ` cvs-commit at gcc dot gnu.org 2014-09-11 12:18 ` cvs-commit at gcc dot gnu.org 2014-09-11 12:38 ` palves at redhat dot com 2014-10-22 18:33 ` naesten at gmail 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-17347-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: linkBe 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).