From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: Infinite loop in sigstep.exp
Date: Mon, 30 Aug 2004 14:05:00 -0000 [thread overview]
Message-ID: <413333F4.5060304@gnu.org> (raw)
In-Reply-To: <4133186C.nailO1B1RC12L@mindspring.com>
> 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.
A [k]failing pattern for:
"Breakpoint .*$gdb_prompt "
would also help.
Andrew
next prev parent reply other threads:[~2004-08-30 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 12:06 Michael Chastain
2004-08-30 14:05 ` Andrew Cagney [this message]
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=413333F4.5060304@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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).