From: Pedro Alves <pedro@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: tracing broken if target doesn't do disconnected tracing
Date: Mon, 05 Apr 2010 11:04:00 -0000 [thread overview]
Message-ID: <201004051204.25151.pedro@codesourcery.com> (raw)
In-Reply-To: <4BB937EC.6080303@codesourcery.com>
On Monday 05 April 2010 02:07:56, Stan Shebs wrote:
> I'm thinking that this is in some ways like the circular trace buffer
> flag, and could be reasonably made accessible via the trace_status
> structure. Unless you're just dying to do this yourself :-) , I'll take
> care of the two together.
Please, be my guest. :-)
> (I can see where this is going longterm - struct trace_status is
> effectively a host-side copy of the agent's state, echoed back in
> response to any instructions that GDB sends down.)
I'd only suggest you keep in mind what will happen when we define
how tracing works with multi-process, as we'll be working on that
soonish. That is, whether with multi-process, there will be a trace
status object per process, while supporting disconnected tracing
or not sounds like a target (debug interface) wide attribute.
--
Pedro Alves
next prev parent reply other threads:[~2010-04-05 11:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 0:01 Pedro Alves
2010-04-05 1:08 ` Stan Shebs
2010-04-05 11:04 ` Pedro Alves [this message]
2010-04-07 1:34 ` Stan Shebs
2010-04-07 11:40 ` Pedro Alves
2010-04-07 13:33 ` Stan Shebs
2010-04-07 13:47 ` Pedro Alves
2010-04-07 14:07 ` Pedro Alves
2010-04-07 20:21 ` Stan Shebs
2010-04-07 22:06 ` Pedro Alves
2010-04-07 13:35 ` Pedro Alves
2010-04-07 22:04 ` Stan Shebs
2010-04-08 17:25 ` Pedro Alves
2010-04-08 18:19 ` Stan Shebs
2010-04-08 18:32 ` Pedro Alves
2010-04-08 19:10 ` Stan Shebs
2010-04-09 3:10 ` Stan Shebs
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=201004051204.25151.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--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