From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Cc: Nick Roberts <nickrob@snap.net.nz>
Subject: Re: [RFC] Fix MI timings
Date: Mon, 09 Mar 2009 21:15:00 -0000 [thread overview]
Message-ID: <200903100015.03600.vladimir@codesourcery.com> (raw)
In-Reply-To: <200903100010.06180.vladimir@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Tuesday 10 March 2009 00:10:05 Vladimir Prus wrote:
> I've noticed that -enable-timings produces broken output for all
> commands that resume target. First, we output *stopped.
> And them on a separate line we print the timing, like this:
>
> ,time={wallclock="0.32046",user="0.32000",system="0.00000"} (gdb)
>
> This happens because mi_on_normal_stop does print newline, and then
> mi_execute_async_cli_command does timings separately. This patch:
>
> 1. Make mi_on_normal_stop emit the timing info
> 2. Stop mi_execute_async_cli_command from doing so
> 3. Makes captured_mi_execute_command report timing both to MI
> and CLI code paths.
>
> I'll commit this in a few days if there are no objections.
*This* patch.
- Volodya
[-- Attachment #2: timing.diff --]
[-- Type: text/x-patch, Size: 3487 bytes --]
diff --git a/gdb/mi/mi-interp.c b/gdb/mi/mi-interp.c
index 65c1b4f..5ab5036 100644
--- a/gdb/mi/mi-interp.c
+++ b/gdb/mi/mi-interp.c
@@ -362,6 +362,7 @@ mi_on_normal_stop (struct bpstats *bs, int print_frame)
fputs_unfiltered ("*stopped", raw_stdout);
mi_out_put (mi_uiout, raw_stdout);
mi_out_rewind (mi_uiout);
+ print_timing_maybe ();
fputs_unfiltered ("\n", raw_stdout);
gdb_flush (raw_stdout);
}
diff --git a/gdb/mi/mi-main.c b/gdb/mi/mi-main.c
index b905a9e..a41c135 100644
--- a/gdb/mi/mi-main.c
+++ b/gdb/mi/mi-main.c
@@ -97,6 +97,8 @@ static void timestamp (struct mi_timestamp *tv);
static void print_diff_now (struct mi_timestamp *start);
static void print_diff (struct mi_timestamp *start, struct mi_timestamp *end);
+void print_timing_maybe ();
+
void
mi_cmd_gdb_exit (char *command, char **argv, int argc)
@@ -1139,7 +1141,8 @@ captured_mi_execute_command (struct ui_out *uiout, void *data)
{
struct mi_parse *context = (struct mi_parse *) data;
- struct mi_timestamp cmd_finished;
+ if (do_timings)
+ current_command_ts = context->cmd_start;
running_result_record_printed = 0;
switch (context->op)
@@ -1151,14 +1154,9 @@ captured_mi_execute_command (struct ui_out *uiout, void *data)
fprintf_unfiltered (raw_stdout, " token=`%s' command=`%s' args=`%s'\n",
context->token, context->command, context->args);
- if (do_timings)
- current_command_ts = context->cmd_start;
mi_cmd_execute (context);
- if (do_timings)
- timestamp (&cmd_finished);
-
/* Print the result if there were no errors.
Remember that on the way out of executing a command, you have
@@ -1174,10 +1172,7 @@ captured_mi_execute_command (struct ui_out *uiout, void *data)
? "^connected" : "^done", raw_stdout);
mi_out_put (uiout, raw_stdout);
mi_out_rewind (uiout);
- /* Have to check cmd_start, since the command could be
- -enable-timings. */
- if (do_timings && context->cmd_start)
- print_diff (context->cmd_start, &cmd_finished);
+ print_timing_maybe ();
fputs_unfiltered ("\n", raw_stdout);
}
else
@@ -1212,7 +1207,8 @@ captured_mi_execute_command (struct ui_out *uiout, void *data)
fputs_unfiltered ("^done", raw_stdout);
mi_out_put (uiout, raw_stdout);
mi_out_rewind (uiout);
- fputs_unfiltered ("\n", raw_stdout);
+ print_timing_maybe ();
+ fputs_unfiltered ("\n", raw_stdout);
}
else
mi_out_rewind (uiout);
@@ -1447,8 +1443,6 @@ mi_execute_async_cli_command (char *cli_command, char **argv, int argc)
/* Do this before doing any printing. It would appear that some
print code leaves garbage around in the buffer. */
do_cleanups (old_cleanups);
- if (do_timings)
- print_diff_now (current_command_ts);
}
}
@@ -1567,6 +1561,15 @@ print_diff_now (struct mi_timestamp *start)
print_diff (start, &now);
}
+void
+print_timing_maybe ()
+{
+ // If the command is -enable-timing then do_timings may be
+ // true whilst current_command_ts is not initialized.
+ if (do_timings && current_command_ts)
+ print_diff_now (current_command_ts);
+}
+
static long
timeval_diff (struct timeval start, struct timeval end)
{
diff --git a/gdb/mi/mi-main.h b/gdb/mi/mi-main.h
index 977579e..6766d71 100644
--- a/gdb/mi/mi-main.h
+++ b/gdb/mi/mi-main.h
@@ -30,5 +30,7 @@ extern char *current_token;
extern int running_result_record_printed;
+void print_timing_maybe ();
+
#endif
next prev parent reply other threads:[~2009-03-09 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 21:10 Vladimir Prus
2009-03-09 21:15 ` Vladimir Prus [this message]
2009-03-09 21:22 ` Daniel Jacobowitz
2009-03-09 21:32 ` Vladimir Prus
2009-03-09 21:36 ` Pedro Alves
2009-03-09 22:07 ` Pedro Alves
2009-03-17 5:27 ` Pedro Alves
2009-03-17 7:26 ` Vladimir Prus
2009-03-17 8:03 ` Vladimir Prus
2009-03-13 7:59 ` Vladimir Prus
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=200903100015.03600.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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