From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com, cagney@gnu.org, eliz@gnu.org
Subject: Re: [rfa/target/doc] Print less with "set debug target 1"
Date: Mon, 08 Mar 2004 22:49:00 -0000 [thread overview]
Message-ID: <404CF878.1030808@redhat.com> (raw)
In-Reply-To: <20040306230834.GA9343@nevyn.them.org>
Daniel Jacobowitz wrote:
> This is something that's always bugged me. I wanted to track a problem in
> the testsuite using "set debug target 1", but the output was so incredibly
> noisy (because of libthread_db) that everything timed out. This patch
> changes "set debug target 1" to only print the first line of a memory
> transfer, and documents "set debug target 2" to print the whole thing.
>
> Seem OK?
>
I think it's a great idea -- my only concern is with legacy issues.
But I doubt if more than 3 people in the world ever use it, so I'm
in favor.
M
WARNING: multiple messages have this Message-ID
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com, cagney@gnu.org, eliz@gnu.org
Subject: Re: [rfa/target/doc] Print less with "set debug target 1"
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <404CF878.1030808@redhat.com> (raw)
Message-ID: <20040319000900.BupXgXPfZS_-6gjOUAsU0BrrxVQD2plb4mOhdTGg8yo@z> (raw)
In-Reply-To: <20040306230834.GA9343@nevyn.them.org>
Daniel Jacobowitz wrote:
> This is something that's always bugged me. I wanted to track a problem in
> the testsuite using "set debug target 1", but the output was so incredibly
> noisy (because of libthread_db) that everything timed out. This patch
> changes "set debug target 1" to only print the first line of a memory
> transfer, and documents "set debug target 2" to print the whole thing.
>
> Seem OK?
>
I think it's a great idea -- my only concern is with legacy issues.
But I doubt if more than 3 people in the world ever use it, so I'm
in favor.
M
next prev parent reply other threads:[~2004-03-08 22:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Daniel Jacobowitz
2004-03-06 23:08 ` Daniel Jacobowitz
2004-03-08 22:49 ` Michael Snyder [this message]
2004-03-19 0:09 ` Michael Snyder
2004-03-09 16:18 ` Daniel Jacobowitz
2004-03-19 0:09 ` Eli Zaretskii
2004-03-09 19:39 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-09 19:39 ` Eli Zaretskii
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Eli Zaretskii
2004-03-07 5:39 ` Eli Zaretskii
2004-03-09 0:12 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Michael Snyder
2004-03-08 22:48 ` Michael Snyder
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=404CF878.1030808@redhat.com \
--to=msnyder@redhat.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@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