Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Disconnected tracing
Date: Wed, 06 Jan 2010 18:46:00 -0000	[thread overview]
Message-ID: <833a2jcbtw.fsf@gnu.org> (raw)
In-Reply-To: <4B441D89.6030902@codesourcery.com>

> Date: Tue, 05 Jan 2010 21:20:09 -0800
> From: Stan Shebs <stan@codesourcery.com>
> 
> This next patch realizes a long-anticipated advantage of tracepoints, 
> namely that it should be possible to disconnect GDB from the target but 
> leave the trace experiment running, then reconnect later to see if 
> anything interesting turned up.

Thanks.

> Index: NEWS
> ===================================================================
> RCS file: /cvs/src/src/gdb/NEWS,v
> retrieving revision 1.345
> diff -p -r1.345 NEWS
> *** NEWS	6 Jan 2010 04:20:26 -0000	1.345
> --- NEWS	6 Jan 2010 04:55:19 -0000

This part is okay.

> Index: doc/gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.655
> diff -p -r1.655 gdb.texinfo
> *** doc/gdb.texinfo	6 Jan 2010 04:20:27 -0000	1.655
> --- doc/gdb.texinfo	6 Jan 2010 04:55:20 -0000

A minor comment and a question:

> + ask what you want to do with the trace. But for unexpected
                                          ^^
Two spaces, please.

> + that define tracepoints. (FIXME add detailed syntax)

When will this FIXME be taken care of?

Thanks.


  reply	other threads:[~2010-01-06 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06  5:20 Stan Shebs
2010-01-06 18:46 ` Eli Zaretskii [this message]
2010-01-06 19:23   ` Stan Shebs
2010-01-06 19:45 ` Tom Tromey
2010-01-06 19:56   ` Stan Shebs
2010-01-06 20:13     ` 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=833a2jcbtw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stan@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