public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at parcs dot ath.cx" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/18062] New: Infinite loop when single-step out of syscall
Date: Sat, 28 Feb 2015 15:23:00 -0000	[thread overview]
Message-ID: <bug-18062-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18062
           Summary: Infinite loop when single-step out of syscall
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
          Assignee: unassigned at sourceware dot org
          Reporter: patrick at parcs dot ath.cx

When the inferior is stopped inside a syscall (e.g. poll), single-stepping out
of this syscall (via "step") causes GDB to loop and to slowly consume more and
more memory.  This can easily be seen when debugging GDB with GDB:

$ gdb gdb
(gdb) run
Starting program: /scratchpad/binutils-gdb-build/gdb/gdb 
(gdb) ^C
Program received signal SIGINT, Interrupt.
0x00007ffff6d784f0 in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) step 
Single stepping until exit from function poll,
which has no line number information.
<infinite loop here>

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


             reply	other threads:[~2015-02-28 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28 15:23 patrick at parcs dot ath.cx [this message]
2015-02-28 15:24 ` [Bug breakpoints/18062] " patrick at parcs dot ath.cx
2015-02-28 15:38 ` patrick at parcs dot ath.cx

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-18062-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).