From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Don't allow calling inferior functions in reverse execution mode
Date: Thu, 26 May 2011 16:23:00 -0000 [thread overview]
Message-ID: <201105261723.22519.pedro@codesourcery.com> (raw)
Can't work...
Applied.
--
Pedro Alves
2011-05-26 Pedro Alves <pedro@codesourcery.com>
gdb/
* infcall.c (call_function_by_hand): Don't allow calling functions
in reverse execution mode.
---
gdb/infcall.c | 3 +++
1 file changed, 3 insertions(+)
Index: src/gdb/infcall.c
===================================================================
--- src.orig/gdb/infcall.c 2011-05-26 17:16:02.000000000 +0100
+++ src/gdb/infcall.c 2011-05-26 17:15:57.251253809 +0100
@@ -495,6 +495,9 @@ call_function_by_hand (struct value *fun
if (get_traceframe_number () >= 0)
error (_("May not call functions while looking at trace frames."));
+ if (execution_direction == EXEC_REVERSE)
+ error (_("May not call functions in reverse."));
+
frame = get_current_frame ();
gdbarch = get_frame_arch (frame);
next reply other threads:[~2011-05-26 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 16:23 Pedro Alves [this message]
2011-05-26 16:37 ` Joel Brobecker
2011-05-26 17:21 ` Eli Zaretskii
2011-05-30 16:09 ` Joel Brobecker
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=201105261723.22519.pedro@codesourcery.com \
--to=pedro@codesourcery.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