From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit reverse debugging [4/5]
Date: Thu, 09 Oct 2008 02:39:00 -0000 [thread overview]
Message-ID: <48ED6E13.1040704@vmware.com> (raw)
In-Reply-To: <200810090312.16021.pedro@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Pedro Alves wrote:
> A Thursday 09 October 2008 02:18:08, Michael Snyder wrote:
>> Sorry, it's an artifact of the fact that I've been on a
>> fork for so long. When I copied this code from finish_command,
>> the code that I copied had a similar call to internal_error.
>>
>> In fact, finish_command_continuation still does.
>
> Yeah, the continuation has a check for `function != NULL',
> though.
>
>> In fact, it's the same call that used to be in "finish_command".
>>
>> So what should it be? Just "error"?
>
> Ah, I think I see what's going on. "finish" is not meaningful
> in the outermost frame, so, you'd get an error before reaching
> here, if you had no symbols.
>
> (gdb) finish
> "finish" not meaningful in the outermost frame.
> (gdb) reverse-finish
> "finish" not meaningful in the outermost frame.
>
> Is it possible to be at frame != #0 and not find a function?
I have no idea, I was just checking the return value
on general principals.
[sucking out "frame 0" discussion for separate reply]
>> I think I understand that you think it would be more "local"
>> to put the error here -- but is it worth it if it makes us
>> add complexity?
>>
>> finish_command already tests a number of things, including
>> whether we are async and (now) whether we are reverse, and
>> contains a number of error calls already.
>
> No biggie with me. Just thought you had signed up to do
> the function split. ;-)
Well I didn't, but I will. How does this look to you
(as an add-on to the present patch)?
[-- Attachment #2: finish_forward.txt --]
[-- Type: text/plain, Size: 4367 bytes --]
Index: infcmd.c
===================================================================
RCS file: /cvs/src/src/gdb/infcmd.c,v
retrieving revision 1.212.2.7
diff -u -p -r1.212.2.7 infcmd.c
--- infcmd.c 8 Oct 2008 00:26:28 -0000 1.212.2.7
+++ infcmd.c 9 Oct 2008 02:32:33 -0000
@@ -1370,9 +1370,10 @@ finish_command_continuation_free_arg (vo
/* finish_backward -- helper function for finish_command. */
static void
-finish_backward (struct symbol *function, struct thread_info *tp)
+finish_backward (struct symbol *function)
{
struct symtab_and_line sal;
+ struct thread_info *tp = inferior_thread ();
struct breakpoint *breakpoint;
struct cleanup *old_chain;
CORE_ADDR func_addr;
@@ -1385,8 +1386,6 @@ finish_backward (struct symbol *function
sal = find_pc_line (func_addr, 0);
- /* TODO: Let's not worry about async until later. */
-
/* We don't need a return value. */
tp->proceed_to_finish = 0;
/* Special case: if we're sitting at the function entry point,
@@ -1421,26 +1420,56 @@ finish_backward (struct symbol *function
/* If in fact we hit the step-resume breakpoint (and not
some other breakpoint), then we're almost there --
we just need to back up by one more single-step. */
- /* (Kludgy way of letting wait_for_inferior know...) */
tp->step_range_start = tp->step_range_end = 1;
proceed ((CORE_ADDR) -1, TARGET_SIGNAL_DEFAULT, 1);
}
return;
}
+/* finish_forward -- helper function for finish_command. */
+
+static void
+finish_forward (struct symbol *function, struct frame_info *frame)
+{
+ struct symtab_and_line sal;
+ struct thread_info *tp = inferior_thread ();
+ struct breakpoint *breakpoint;
+ struct cleanup *old_chain;
+ struct finish_command_continuation_args *cargs;
+
+ sal = find_pc_line (get_frame_pc (frame), 0);
+ sal.pc = get_frame_pc (frame);
+
+ breakpoint = set_momentary_breakpoint (sal, get_frame_id (frame),
+ bp_finish);
+
+ old_chain = make_cleanup_delete_breakpoint (breakpoint);
+
+ tp->proceed_to_finish = 1; /* We want stop_registers, please... */
+ make_cleanup_restore_integer (&suppress_stop_observer);
+ suppress_stop_observer = 1;
+ proceed ((CORE_ADDR) -1, TARGET_SIGNAL_DEFAULT, 0);
+
+ cargs = xmalloc (sizeof (*cargs));
+
+ cargs->breakpoint = breakpoint;
+ cargs->function = function;
+ add_continuation (tp, finish_command_continuation, cargs,
+ finish_command_continuation_free_arg);
+
+ discard_cleanups (old_chain);
+ if (!target_can_async_p ())
+ do_all_continuations ();
+}
+
/* "finish": Set a temporary breakpoint at the place the selected
frame will return to, then continue. */
static void
finish_command (char *arg, int from_tty)
{
- struct symtab_and_line sal;
struct frame_info *frame;
struct symbol *function;
- struct breakpoint *breakpoint;
- struct cleanup *old_chain;
- struct finish_command_continuation_args *cargs;
- struct thread_info *tp;
int async_exec = 0;
@@ -1474,8 +1503,6 @@ finish_command (char *arg, int from_tty)
if (frame == 0)
error (_("\"finish\" not meaningful in the outermost frame."));
- tp = inferior_thread ();
-
clear_proceed_status ();
/* Find the function we will return from. */
@@ -1495,35 +1522,9 @@ finish_command (char *arg, int from_tty)
}
if (execution_direction == EXEC_REVERSE)
- {
- /* Split off at this point. */
- finish_backward (function, tp);
- return;
- }
-
- sal = find_pc_line (get_frame_pc (frame), 0);
- sal.pc = get_frame_pc (frame);
-
- breakpoint = set_momentary_breakpoint (sal, get_frame_id (frame),
- bp_finish);
-
- old_chain = make_cleanup_delete_breakpoint (breakpoint);
-
- tp->proceed_to_finish = 1; /* We want stop_registers, please... */
- make_cleanup_restore_integer (&suppress_stop_observer);
- suppress_stop_observer = 1;
- proceed ((CORE_ADDR) -1, TARGET_SIGNAL_DEFAULT, 0);
-
- cargs = xmalloc (sizeof (*cargs));
-
- cargs->breakpoint = breakpoint;
- cargs->function = function;
- add_continuation (tp, finish_command_continuation, cargs,
- finish_command_continuation_free_arg);
-
- discard_cleanups (old_chain);
- if (!target_can_async_p ())
- do_all_continuations ();
+ finish_backward (function);
+ else
+ finish_forward (function, frame);
}
\f
next prev parent reply other threads:[~2008-10-09 2:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 2:22 Michael Snyder
2008-10-08 23:38 ` Pedro Alves
2008-10-08 23:55 ` Michael Snyder
2008-10-09 0:36 ` Pedro Alves
2008-10-09 1:20 ` Michael Snyder
2008-10-09 2:12 ` Pedro Alves
2008-10-09 2:39 ` Michael Snyder [this message]
2008-10-09 3:21 ` Pedro Alves
2008-10-09 2:49 ` Michael Snyder
2008-10-09 3:11 ` Pedro Alves
2008-10-17 19:47 ` Michael Snyder
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=48ED6E13.1040704@vmware.com \
--to=msnyder@vmware.com \
--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