From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21135 invoked by alias); 23 Aug 2014 16:07:27 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 21099 invoked by uid 48); 23 Aug 2014 16:07:26 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/17247] gdb freezes on multi threaded app (test-case attached) Date: Sat, 23 Aug 2014 16:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at google dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q3/txt/msg00317.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17247 --- Comment #14 from dje at google dot com --- (In reply to Bernd Amend from comment #13) > I encountered this issue on Archlinux with gdb 7.8. > I bisected the issue to the commit > > commit ed3ef33944c39d9a3cea72b9a7cef3c20f0e3461 > Author: Doug Evans > Date: Sun Feb 9 19:40:01 2014 -0800 > > Add Guile as an extension language. > > I hope this helps to track down the issue. I'm not sure how much help a bisect can be here is the issue is a race condition. But you have given me an idea. Guile uses a separate thread to help with garbage collection, and perhaps a SIGCHLD is being lost somehow (or whatever). Question: Does the bug go away if you configure gdb --without-guile? [Assuming you've got guile installed and the buggy gdb was configured with it.] -- You are receiving this mail because: You are on the CC list for the bug.