From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] mips32 frame code simplification...
Date: Wed, 15 Sep 2004 19:57:00 -0000 [thread overview]
Message-ID: <41489DF5.3020104@gnu.org> (raw)
In-Reply-To: <414879E3.nailB7Z1MJFFM@mindspring.com>
> Joel Brobecker writes:
>
>>> 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.
>
>
> How about:
>
> set backtrace limit 1000
>
> That would look good in default_gdb_start and mi_gdb_start.
Someone somewhere pointed out (with a patch) that
set backtrace limit 1000
didn't actually work! I've lost the patch but am working on a tested fix.
Now if only I could remember who posted the original patch.
Andrew
> However a backtrace limit of 1000 would still overflow the
> 20000-character buffer. Also I've heard that "set backtrace limit"
> has a bug these days.
>
> We could also change the individual "backtrace" and "bt" calls to
> "backtrace 100". That's simpler and more effective, but it fixes
> just one nit at a time.
>
>
>>> 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?
>
>
> I don't know enough about expect to get into that area. :(
>
next prev parent reply other threads:[~2004-09-15 19:57 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
2004-09-15 17:20 ` Michael Chastain
2004-09-15 19:57 ` Andrew Cagney [this message]
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=41489DF5.3020104@gnu.org \
--to=cagney@gnu.org \
--cc=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