From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: drow@false.org, carlton@kealia.com, ezannoni@redhat.com,
gdb@sources.redhat.com
Subject: Re: Huge slowdown since 6.0
Date: Mon, 23 Feb 2004 19:22:00 -0000 [thread overview]
Message-ID: <403A52ED.7080908@gnu.org> (raw)
In-Reply-To: <20040220195722.D195E4B104@berman.michael-chastain.com>
> ac> It's been suggested to me that we should create a hacked gdb that
> ac> records all commands et.al. to a file, and then offers to send them to
> ac> us. That way we know what is, rather than what might be.
>
> I think we can do this just with doco. In the doco that says how
> to report bugs, add some basic instructions on the "script" command.
True, or even just by looking at the bug reports.
Andrew
next prev parent reply other threads:[~2004-02-23 19:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 19:57 Michael Elizabeth Chastain
2004-02-23 19:22 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 21:09 Daniel Jacobowitz
2004-02-18 21:31 ` David Carlton
2004-02-18 22:45 ` Kip Macy
2004-02-19 3:35 ` Daniel Jacobowitz
2004-02-19 5:06 ` Kip Macy
2004-02-19 15:40 ` Daniel Jacobowitz
2004-02-20 5:09 ` Daniel Jacobowitz
2004-02-20 16:42 ` Elena Zannoni
2004-02-20 16:47 ` Daniel Jacobowitz
2004-02-20 17:33 ` Elena Zannoni
2004-02-20 17:01 ` Andrew Cagney
2004-02-20 17:05 ` Daniel Jacobowitz
2004-02-20 17:45 ` Elena Zannoni
2004-02-20 18:07 ` Andrew Cagney
2004-02-20 18:24 ` Daniel Jacobowitz
2004-02-20 18:45 ` Andrew Cagney
2004-02-20 18:48 ` Daniel Jacobowitz
2004-02-21 9:21 ` Eli Zaretskii
2004-02-21 9:04 ` Eli Zaretskii
2004-02-21 2:18 ` Daniel Jacobowitz
2004-02-20 16:52 ` David Carlton
2004-02-20 16:58 ` Daniel Jacobowitz
2004-02-20 17:00 ` David Carlton
2004-02-20 17:35 ` Elena Zannoni
2004-02-19 1:59 ` Elena Zannoni
2004-02-19 3:35 ` Daniel Jacobowitz
2004-02-19 3:58 ` 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=403A52ED.7080908@gnu.org \
--to=cagney@gnu.org \
--cc=carlton@kealia.com \
--cc=drow@false.org \
--cc=ezannoni@redhat.com \
--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