public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "matthijstijink at hotmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/9585] GNU/Linux x86, gdb freezes after fork wit detach-on-fork off and follow-fork-mode child Date: Mon, 02 Nov 2009 17:30:00 -0000 [thread overview] Message-ID: <20091102173016.21145.qmail@sourceware.org> (raw) In-Reply-To: <20080721155802.9585.aviseldom@infonegocio.com> ------- Additional Comments From matthijstijink at hotmail dot com 2009-11-02 17:30 ------- I confirm this behaviour. I didn't use wine, but with a lot of programs I tried gdb just hangs. I tried running a simple bash script but even that doesn't work. Sometimes Ctrl-C can stop the process so you can quit gdb, but other times gdb hangs and I have to kill it. If you use 'set print inferior-events', you see that the new process is started, but nothing happens. -- http://sourceware.org/bugzilla/show_bug.cgi?id=9585 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next parent reply other threads:[~2009-11-02 17:30 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20080721155802.9585.aviseldom@infonegocio.com> 2009-11-02 17:30 ` matthijstijink at hotmail dot com [this message] 2009-11-02 17:32 ` matthijstijink at hotmail dot com 2010-04-06 6:29 ` flavio dot etrusco at gmail dot com 2010-04-06 10:33 ` pedro at codesourcery dot com 2010-04-07 23:03 ` flavio dot etrusco at gmail dot com 2010-04-07 23:11 ` flavio dot etrusco at gmail dot com 2010-04-07 23:33 ` pedro at codesourcery dot com 2010-04-08 1:25 ` flavio dot etrusco at gmail dot com 2010-04-08 1:26 ` flavio dot etrusco at gmail dot com 2010-04-08 1:28 ` flavio dot etrusco at gmail dot com 2010-04-08 15:19 ` pedro at codesourcery dot com [not found] <bug-9585-4717@http.sourceware.org/bugzilla/> 2012-10-24 15:52 ` palves at redhat dot com 2012-10-24 15:52 ` 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=20091102173016.21145.qmail@sourceware.org \ --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).