From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: Don't allow calling inferior functions in reverse execution mode
Date: Mon, 30 May 2011 16:09:00 -0000 [thread overview]
Message-ID: <20110530160921.GC2620@adacore.com> (raw)
In-Reply-To: <83sjs1cr9u.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 135 bytes --]
> How about
>
> Cannot call functions in reverse mode.
That's a good suggestion, so I applied it as attached...
Thanks!
--
Joel
[-- Attachment #2: infcall.diff --]
[-- Type: text/x-diff, Size: 1226 bytes --]
commit 01630be116f8e3e5eb5791d29fef5af99305a40c
Author: Joel Brobecker <brobecker@adacore.com>
Date: Mon May 30 08:59:07 2011 -0700
Rephrase error message in infcall.c:call_function_by_hand
No real change besides the error message.
gdb/ChangeLog:
* infcall.c (call_function_by_hand): Rephrase error message.
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 83203a2..7a60b8e 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2011-05-30 Joel Brobecker <brobecker@adacore.com>
+
+ * infcall.c (call_function_by_hand): Rephrase error message.
+
2011-05-27 Pedro Alves <pedro@codesourcery.com>
* defs.h (struct thread_info, struct inferior): Delete forward
diff --git a/gdb/infcall.c b/gdb/infcall.c
index 4063b7f..6553e2a 100644
--- a/gdb/infcall.c
+++ b/gdb/infcall.c
@@ -496,7 +496,7 @@ call_function_by_hand (struct value *function, int nargs, struct value **args)
error (_("May not call functions while looking at trace frames."));
if (execution_direction == EXEC_REVERSE)
- error (_("May not call functions in reverse."));
+ error (_("Cannot call functions in reverse mode."));
frame = get_current_frame ();
gdbarch = get_frame_arch (frame);
prev parent reply other threads:[~2011-05-30 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 16:23 Pedro Alves
2011-05-26 16:37 ` Joel Brobecker
2011-05-26 17:21 ` Eli Zaretskii
2011-05-30 16:09 ` Joel Brobecker [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=20110530160921.GC2620@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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