From: Jim Blandy <jimb@codesourcery.com>
To: "Doug Evans" <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: mention gdb/gdbserver/README in gdb/README
Date: Thu, 17 Jan 2008 00:13:00 -0000 [thread overview]
Message-ID: <m3bq7l5myo.fsf@codesourcery.com> (raw)
In-Reply-To: <e394668d0801161516r7d26d68ar2ff1f842876f8af0@mail.gmail.com> (Doug Evans's message of "Wed, 16 Jan 2008 15:16:33 -0800")
"Doug Evans" <dje at google.com> writes:
> On Jan 16, 2008 2:56 PM, Jim Blandy <jimb@codesourcery.com> wrote:
>>
>> Does this change look okay?
>>
>> gdb/ChangeLog:
>> 2008-01-16 Jim Blandy <jimb@codesourcery.com>
>>
>> * README: Doc fix.
>>
>> diff -r 79c1d0c9402b gdb/README
>> --- a/gdb/README Tue Jan 15 10:14:02 2008 -0800
>> +++ b/gdb/README Wed Jan 16 14:55:33 2008 -0800
>> @@ -453,6 +453,10 @@ allows remote debugging for Unix applica
>> allows remote debugging for Unix applications. gdbserver is only
>> supported for some native configurations, including Sun 3, Sun 4, and
>> Linux.
>> +The file gdb/gdbserver/README includes further notes on gdbserver; in
>> +particular, it explains how to build gdbserver for cross-debugging
>> +(where gdbserver runs on the target machine, which is of a different
>> +architecture than the host machine running GDB).
>>
>> There are a number of remote interfaces for talking to existing ROM
>> monitors and other hardware:
>>
>
> Heh. I grepped through *.texinfo but missed gdbserver/README. Blech.
>
> Not that I care now that it's burned into my memory, but I wonder to
> what extent things in gdb/README, gdb/gdbserver/README, etc. might be
> better placed in foo.texinfo.
Nah. Trauma is just as good as documentation.
:)
next prev parent reply other threads:[~2008-01-17 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 22:57 Jim Blandy
2008-01-16 23:17 ` Doug Evans
2008-01-17 0:13 ` Jim Blandy [this message]
2008-01-17 4:18 ` Eli Zaretskii
2008-01-17 20:23 ` Jim Blandy
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=m3bq7l5myo.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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