From: Jim Blandy <jimb@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: mention gdb/gdbserver/README in gdb/README
Date: Thu, 17 Jan 2008 20:23:00 -0000 [thread overview]
Message-ID: <m3r6ggmcbo.fsf@codesourcery.com> (raw)
In-Reply-To: <ud4s1ozka.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Jan 2008 06:17:57 +0200")
Eli Zaretskii <eliz at gnu.org> writes:
>> From: Jim Blandy <jimb@codesourcery.com>
>> Date: Wed, 16 Jan 2008 14:56:53 -0800
>>
>>
>> Does this change look okay?
>
> Yes, but maybe the ChangeLog entry should be more descriptive ("doc
> fix" for a change in README says absolutely nothing).
Committed as follows --- thanks.
gdb/ChangeLog:
2008-01-17 Jim Blandy <jimb@codesourcery.com>
* README: Mention gdbserver/README.
diff -r 9ed5b2935471 gdb/README
--- a/gdb/README Thu Jan 17 11:42:36 2008 -0800
+++ b/gdb/README Thu Jan 17 12:17:13 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:
prev parent reply other threads:[~2008-01-17 20:23 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
2008-01-17 4:18 ` Eli Zaretskii
2008-01-17 20:23 ` Jim Blandy [this message]
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=m3r6ggmcbo.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=eliz@gnu.org \
--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