From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: eliz@gnu.org, kettenis@chello.nl
Cc: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: [6.2] PROBLEMS file
Date: Thu, 22 Jul 2004 12:14:00 -0000 [thread overview]
Message-ID: <20040722093553.624FF4B104@berman.michael-chastain.com> (raw)
Mark Kettenis writes:
> There will always be cases where GDB will get confused and lose track.
> In that case it will possibly provide an endless or very long backtrace
> containing garbage.
I'm okay with this part, as long as the user can easily get it
out of it at the "press space to continue" prompt.
It would be nice to have an adjustable cutoff defaulting to perhaps
1000 or 10,000 frames. I've had some huge gdb.log files
(20 megabytes) because the test suite triggered such a bug and
then gdb wouldn't quit.
> So IMHO there is no regression here. PR 1505 should be closed.
It's a regression if a specific sequence of commands works with
gdb N and does not work with gdb N+1. You might have to say
"can't fix" or "won't fix".
Michael C
next reply other threads:[~2004-07-22 9:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 12:14 Michael Elizabeth Chastain [this message]
2004-07-22 18:28 ` Joel Brobecker
2004-07-22 19:26 ` Eli Zaretskii
2004-07-22 20:51 ` Mark Kettenis
2004-07-23 9:24 ` Eli Zaretskii
2004-07-23 11:22 ` Mark Kettenis
2004-07-23 12:03 ` Eli Zaretskii
2004-07-23 12:13 ` Eli Zaretskii
2004-07-23 12:16 ` Dave Korn
2004-07-23 13:36 ` Mark Kettenis
2004-07-23 16:17 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-07-23 5:44 Michael Elizabeth Chastain
2004-07-23 20:44 ` Andrew Cagney
2004-07-19 3:51 Andrew Cagney
2004-07-19 21:01 ` Eli Zaretskii
2004-07-21 21:12 ` Mark Kettenis
2004-07-21 22:05 ` H. J. Lu
2004-07-22 20:58 ` Mark Kettenis
2004-07-22 21:33 ` Joel Brobecker
2004-07-22 21:38 ` H. J. Lu
2004-07-21 22:17 ` Andrew Cagney
2004-07-22 7:13 ` Eli Zaretskii
2004-07-22 13:04 ` Dave Korn
2004-07-22 15:17 ` 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=20040722093553.624FF4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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).