public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andy.somogyi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18449] New: GDB crashes on OSX
Date: Fri, 22 May 2015 15:39:00 -0000	[thread overview]
Message-ID: <bug-18449-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=18449

            Bug ID: 18449
           Summary: GDB crashes on OSX
           Product: gdb
           Version: 7.9
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: andy.somogyi at gmail dot com
  Target Milestone: ---

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. 

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. 

On OSX 10.7, when using the built in GDB 6.3, no problems are found. However,
when installing GDB 7.9 from homebrew, the problem exists. On two other
machines, with OSX 10.9 and 10.10, has the same problems with GDB 7.7 and 7.9
and 7.9.1  

This is using GDB through eclipse. 

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2015-05-22 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 15:39 andy.somogyi at gmail dot com [this message]
2015-05-22 18:17 ` [Bug gdb/18449] " keiths 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=bug-18449-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).