From: Dmitry Kozlov <dmitry_kozlov@mentor.com>
To: Hui Zhu <teawater@gmail.com>
Cc: <gdb-patches@sourceware.org>, Pedro Alves <palves@redhat.com>,
Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: [PATCH 2 OF 2] extend tsave to write start and stop time into a trace file
Date: Mon, 10 Jun 2013 14:21:00 -0000 [thread overview]
Message-ID: <51B5D080.4080206@mentor.com> (raw)
In-Reply-To: <CANFwon3xBZpYJMqqKYOHvEp05cBGYfMeEsGA9L0qBmVJxVSKeQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
On 06/10/2013 05:08 PM, Hui Zhu wrote:
> On Mon, Jun 10, 2013 at 8:47 PM, Dmitry Kozlov <dmitry_kozlov@mentor.com> wrote:
>> Hi Pedro,
>> some time ago we already discussed these patches, could you please review
>> them again.
>>
>> And this one extends tsave command to write start and stop time into a
>> tracefile.
>>
>>
>> Thank you,
>> Dmitry
>>
> This patch gdb_1_of_2_tstatus.diff is not the right one?
Sure, proper attached. Thank you!
> Thanks,
> Hui
[-- Attachment #2: gdb_2_of_2_tsave.diff --]
[-- Type: text/x-patch, Size: 1395 bytes --]
commit 47fa5083c22982ea135156ac8c2e67d222190781
Author: Dmitry Kozlov <dmitry_kozlov@mentor.com>
Date: Mon Jun 10 16:30:49 2013 +0400
Extend tsave to save starttime, stoptime.
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 561d93b..c775e34 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,9 @@
2013-06-10 Dmitry Kozlov <ddk@codesourcery.com>
+ * tracepoint.c (trace_save): Extend tsave to save starttime, stoptime.
+
+2013-06-10 Dmitry Kozlov <ddk@codesourcery.com>
+
Fix trace-status to output proper start-time and stop-time.
* tracepoint.c (trace_status_command): Fix type of printf arg to
prevent improper type conversion.
diff --git a/gdb/tracepoint.c b/gdb/tracepoint.c
index 38362b4..6af88f5 100644
--- a/gdb/tracepoint.c
+++ b/gdb/tracepoint.c
@@ -3138,6 +3138,16 @@ tfile_write_status (struct trace_file_writer *self,
fprintf (writer->fp, ";disconn:%x", ts->disconnected_tracing);
if (ts->circular_buffer)
fprintf (writer->fp, ";circular:%x", ts->circular_buffer);
+ if (ts->start_time)
+ {
+ fprintf (writer->fp, ";starttime:%s",
+ phex_nz (ts->start_time, sizeof (ts->start_time)));
+ }
+ if (ts->stop_time)
+ {
+ fprintf (writer->fp, ";stoptime:%s",
+ phex_nz (ts->stop_time, sizeof (ts->stop_time)));
+ }
if (ts->notes != NULL)
{
char *buf = (char *) alloca (strlen (ts->notes) * 2 + 1);
next prev parent reply other threads:[~2013-06-10 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 13:08 Dmitry Kozlov
2013-06-10 13:11 ` Hui Zhu
2013-06-10 14:21 ` Dmitry Kozlov [this message]
2013-06-20 0:41 ` Stan Shebs
2013-06-20 15:18 ` Pedro Alves
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=51B5D080.4080206@mentor.com \
--to=dmitry_kozlov@mentor.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=teawater@gmail.com \
--cc=vladimir@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