From: Michael Chastain <mec.gnu@mindspring.com>
To: cagney@gnu.org
Cc: gdb@sources.redhat.com
Subject: Re: Infinite loop in sigstep.exp
Date: Mon, 30 Aug 2004 15:40:00 -0000 [thread overview]
Message-ID: <41334A6F.nailEET1NDWIK@mindspring.com> (raw)
In-Reply-To: <413333F4.5060304@gnu.org>
This change seems to do the job:
- exp_continue
+ exp_continue -continue_timer
"-continue_timer" means that exp_continue does not reset the timeout
counter for "expect". So after the usual 120 seconds, gdb_test_multiple
busts out with a normal looking timeout FAIL.
I have to check that -continue_timer works with the vintage 1998
"expect" in sourceware.
ac> A [k]failing pattern for:
ac>
ac> "Breakpoint .*$gdb_prompt "
ac>
ac> would also help.
Yes, it would. It would give a nice specific result, but just for this
one case. If you want to submit a patch for that, go for it.
I'm gonna experiment some more with "-continue_timer" which ought to
break all cases of infinite loops.
prev parent reply other threads:[~2004-08-30 15:40 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
2004-08-30 15:40 ` Michael Chastain [this message]
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=41334A6F.nailEET1NDWIK@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