From: Michael Chastain <mec.gnu@mindspring.com>
To: cagney@gnu.org, gdb@sources.redhat.com
Subject: Infinite loop in sigstep.exp
Date: Mon, 30 Aug 2004 12:06:00 -0000 [thread overview]
Message-ID: <4133186C.nailO1B1RC12L@mindspring.com> (raw)
I'm getting an infinite loop in the new sigstep.exp
with an old gdb, gdb drow_intercu-20040221-branch.
gdb.log looks like this:
Breakpoint 2, handler (sig=26) at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/sigstep.c:31
31 done = 1;
1: x/i $pc 0x8048473 <handler+3>: movl $0x1,0x8049738
(gdb) stepi
32 } /* handler */
1: x/i $pc 0x804847d <handler+13>: mov %ebp,%esp
(gdb) stepi
0x0804847f 32 } /* handler */
1: x/i $pc 0x804847f <handler+15>: pop %ebp
(gdb) stepi
0x08048480 in handler (sig=1) at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/sigstep.c:32
32 } /* handler */
1: x/i $pc 0x8048480 <handler+16>: ret
(gdb) stepi
Breakpoint 2, handler (sig=26) at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/sigstep.c:31
31 done = 1;
1: x/i $pc 0x8048473 <handler+3>: movl $0x1,0x8049738
Somehow, stepi off the "ret" instruction just goes back to the
beginning of the function instead of stepping into "<signal handler
called">.
This blows up my test bed, so I have to fix it.
My first plan is to add some counters to prevent infinite loops
with "exp_continue". I'm open to other ideas.
Michael
next reply other threads:[~2004-08-30 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 12:06 Michael Chastain [this message]
2004-08-30 14:05 ` Andrew Cagney
2004-08-30 15:40 ` Michael Chastain
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=4133186C.nailO1B1RC12L@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
/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).