public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gdb-bugs0000 at cneufeld dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/11408] New: gdb-7.1 spins and hangs in my normal work.  (git bisection supplied)
Date: Sat, 20 Mar 2010 19:00:00 -0000	[thread overview]
Message-ID: <20100320190024.11408.gdb-bugs0000@cneufeld.ca> (raw)

I downloaded and compiled gdb-7.1, and found it to be unusable for me.  Whereas
gdb-7.0.1 worked well, 7.1 will often freeze when doing simple things like
setting a new breakpoint at a specified line number.  An strace of the gdb
process shows it to be spinning hard, calling the lseek() syscall over and over
(several thousand times is typical), before completing.  Setting a breakpoint
can take anywhere from 5 seconds to several minutes, with the CPU hard-spinning
the whole time.  This is entirely reproducible for me, I have just to set a
breakpoint at main(), run my debugging binary, then type "b 200" to add another
breakpoint at line 200 in the source module holding main.  This takes several
seconds in 7.1, and is effectively instantaneous in 7.0.1.  I have also seen it
hang when asked to print the value of a local variable.

I compiled gdb from sources, using gcc-4.2.4.

I realize that the git tree isn't fine-grained to individual commits, but having
the bisection ought still to help.  The bad behaviour first appears at revision
f03d5cd98559bdc7ee93b72383d9e50999310a97.  It was fixed at revision
f89f0ae081112db5dfad6264f481e6ca88b4d252, but unfortunately that revision is not
in the 7.1 release.

I've had to revert to 7.0.1 because of this bug.

-- 
           Summary: gdb-7.1 spins and hangs in my normal work.  (git
                    bisection supplied)
           Product: gdb
           Version: 7.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: breakpoints
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: gdb-bugs0000 at cneufeld dot ca
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=11408

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2010-03-20 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20 19:00 gdb-bugs0000 at cneufeld dot ca [this message]
2010-03-22 15:41 ` [Bug breakpoints/11408] " swagiaal at redhat dot com
2010-03-23 14:05 ` glibcbugs0000 at cneufeld dot ca
2010-03-23 15:38 ` swagiaal at redhat dot com
2010-03-23 15:40 ` swagiaal at redhat dot com
2010-03-23 15:44 ` glibcbugs0000 at cneufeld dot ca
2010-03-23 15:48 ` swagiaal at redhat dot com
2010-08-06 19:56 ` tromey at redhat dot com
2010-08-09 16:45 ` tromey 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=20100320190024.11408.gdb-bugs0000@cneufeld.ca \
    --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).