From: Joel Brobecker <brobecker@gnat.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] mips32 frame code simplification...
Date: Wed, 15 Sep 2004 16:29:00 -0000 [thread overview]
Message-ID: <20040915162937.GU5843@gnat.com> (raw)
In-Reply-To: <414844E4.nail2UE22SZGZ@mindspring.com>
> > Frankly, I have reached a point with dejagnu where I just want to
> > throw it out the window, trample it, chop it, burn it, curse it,
> > bury it face down, etc.
>
> Yeah, welcome to the club. Here's your membership card and baseball bat.
Aaah, feel better now :-).
> > I think it's OK for now, but Michael might
> > want to crucify me for suggesting that it's OK.
>
> Naw, we always have to start from wherever we are.
Great.
> In the signals tests, are you getting another exp_continue loop?
> I found that "exp_continue -continue_timer" worked well.
> See sigstep.exp.
I don't think that's the problem. I get an infinite loop inside GDB
itself (backtracing from a signal handler I think), and that causes
the expect/dejagnu buffer to get full. And apparently, this just
disables dejagnu for the rest of the run (can't spawn the compiler
nor the debugger anymore for instance). Maybe there is a way of
flushing that buffer when we do a gdb_exit?
--
Joel
next prev parent reply other threads:[~2004-09-15 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 6:26 Joel Brobecker
2004-09-15 13:34 ` Michael Chastain
2004-09-15 16:29 ` Joel Brobecker [this message]
2004-09-15 17:20 ` Michael Chastain
2004-09-15 19:57 ` Andrew Cagney
2004-09-15 17:33 ` Andrew Cagney
2004-09-16 0:37 ` Joel Brobecker
2004-09-16 13:38 ` Daniel Jacobowitz
2004-09-16 17:33 ` Andrew Cagney
2004-09-16 17:35 ` Daniel Jacobowitz
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=20040915162937.GU5843@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@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