From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 62946 invoked by alias); 22 May 2015 18:17:14 -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 62921 invoked by uid 48); 22 May 2015 18:17:13 -0000 From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18449] GDB crashes on OSX Date: Fri, 22 May 2015 18:17: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.9 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2015-q2/txt/msg00313.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=18449 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #1 from Keith Seitz --- (In reply to Andy Somogyi from comment #0) > When debugging any non-trivial program, such as the python interpreter, or > virtually any other non-trivial program, gdb will hang on OSX with 100% cpu > usage. If you could attach GDB to that hung (GDB) process and send in a backtrace, that might prove really helpful. *Very* few of us active developers have Mac-based systems. [gdb /path/to/gdb -p $pid_of_gdb -ex "thread apply all bt" should do the trick] > The problem started somewhere after 6.3, as the Apple provided GDB 6.3 works > perfectly. I've verified this problem with GDB 7.9 and 7.7. Also verified > this on 3 different machines, with 3 different OSX versions. For the record, 6.3 (Apple's version) is not really FSF GDB. It was heavily modified (as was GCC) by Apple and its related community. Comparing Apple 6.3 vs FSF GDB therefore only tells me that it is likely some modification that was never submitted/accepted/committed in upstream FSF GDB. > On OSX 10.7, when using the built in GDB 6.3, no problems are found. > The initial breakpoint in main is always found just fine, and the first 3-4 > breakpoints are also found, then after say 3-4 continues, gdb itself will > hang with 100% cpu usage. To even begin to help out, we're going to need you to run gdb independently of Eclipse. That one step alone will help us isolate the problem all the quicker. Other useful information: What compiler/version are you using? [I'm assuming Apple's or MacPorts GCC.] -- You are receiving this mail because: You are on the CC list for the bug.