From: Andrew STUBBS <andrew.stubbs@st.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sources.redhat.com
Subject: Re: RFC: GDB as a loader 3/3: --eval-command option
Date: Mon, 07 Nov 2005 18:06:00 -0000 [thread overview]
Message-ID: <436F9700.6050709@st.com> (raw)
In-Reply-To: <20051107172715.GE1635@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 299 bytes --]
Joel Brobecker wrote:
> Indeed, I think you need to add a new section like this:
>
> *** Changes since GDB 6.4
OK, how about the attached? There's one for the branch and one for mainline.
I added the new stuff above the deprecated stuff rather than just
appeanding it to the end.
Andrew Stubbs
[-- Attachment #2: main-news.patch --]
[-- Type: text/plain, Size: 1212 bytes --]
2005-11-07 Andrew Stubbs <andrew.stubbs@st.com>
* NEWS: Change 'since 6.3' to 'in 6.4' and add --batch-silent option.
Add 'since 6.4' section with --return-child-result and --eval-command
options.
Index: src/gdb/NEWS
===================================================================
--- src.orig/gdb/NEWS 2005-11-07 17:37:18.000000000 +0000
+++ src/gdb/NEWS 2005-11-07 17:45:23.000000000 +0000
@@ -1,7 +1,18 @@
What has changed in GDB?
(Organized release by release)
-*** Changes since GDB 6.3
+*** Changes since GDB 6.4
+
+* New command line options
+
+--return-child-result The debugger will exist with the same value
+ the child (debugged) program exited with.
+--eval-command COMMAND, -ex COMMAND
+ Execute a single GDB CLI command. This may be
+ specified multiple times and in conjunction
+ with the --command (-x) option.
+
+*** Changes in GDB 6.4
* New native configurations
@@ -12,6 +23,10 @@ OpenBSD/mips64 mips64-*-openbsd*
Morpho Technologies ms1 ms1-elf
+* New command line options
+
+--batch-silent As for --batch, but totally silent.
+
* Deprecated commands removed
The following commands, that were deprecated in 2000, have been
[-- Attachment #3: 6.4-news.patch --]
[-- Type: text/plain, Size: 560 bytes --]
2005-11-07 Andrew Stubbs <andrew.stubbs@st.com>
* NEWS: Add --batch-silent option.
Index: src6.4/NEWS
===================================================================
--- src6.4.orig/NEWS 2005-11-07 14:12:02.000000000 +0000
+++ src6.4/NEWS 2005-11-07 14:12:08.000000000 +0000
@@ -12,6 +12,10 @@ OpenBSD/mips64 mips64-*-openbsd*
Morpho Technologies ms1 ms1-elf
+* New command line options
+
+--batch-silent As for --batch, but totally silent.
+
* Deprecated commands removed
The following commands, that were deprecated in 2000, have been
next prev parent reply other threads:[~2005-11-07 18:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 11:33 Andrew STUBBS
2005-10-28 11:10 ` Andrew STUBBS
2005-10-28 13:04 ` Eli Zaretskii
2005-10-28 14:03 ` Andrew STUBBS
2005-10-28 17:05 ` Eli Zaretskii
2005-11-04 11:54 ` Andrew STUBBS
2005-11-05 2:51 ` Daniel Jacobowitz
2005-11-05 10:01 ` Eli Zaretskii
2005-11-07 14:01 ` Andrew STUBBS
2005-11-07 14:16 ` Andrew STUBBS
2005-11-07 17:27 ` Joel Brobecker
2005-11-07 18:06 ` Andrew STUBBS [this message]
2005-11-07 20:54 ` Eli Zaretskii
2005-11-07 20:46 ` Eli Zaretskii
2005-11-08 11:05 ` Andrew STUBBS
2005-11-13 17:38 ` Daniel Jacobowitz
2005-11-14 11:45 ` Andrew STUBBS
[not found] ` <20051114134816.GA21373@nevyn.them.org>
2005-11-14 15:57 ` Andrew STUBBS
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=436F9700.6050709@st.com \
--to=andrew.stubbs@st.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).