From: Stan Shebs <stan@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
Marc Khouzam <marc.khouzam@ericsson.com>,
Stan Shebs <stan@codesourcery.com>
Subject: Re: [PATCH] No resuming while tfinding
Date: Wed, 17 Mar 2010 17:31:00 -0000 [thread overview]
Message-ID: <4BA111CB.3050000@codesourcery.com> (raw)
In-Reply-To: <201003171521.59901.pedro@codesourcery.com>
Pedro Alves wrote:
> On Wednesday 17 March 2010 01:59:24, Stan Shebs wrote:
>
>> So I propose that we make an executive decision to disable all the
>> resumption commands while in tfind mode. Does this make sense to everyone?
>>
>
> I object to not making this change. :-)
>
> We should look at tfind mode as sort of a different
> target. It's is kind of similar to debugging a core dump
> while still connecting to a live target.
Yeah, this is one of those places where we wish the target stack was
actually as flexible as it was envisioned to be.
Once we get a tracepoint-supporting gdbserver, perhaps someone can just
try the experiment of creating a tfind target. It might not need
anything more hairy than some explicit calls down into the target stack,
for instance to read memory using the target that is actually storing
the collected data.
I can see users really really liking it if resumption commands were to
work and do the expected things - and now we have reverse execution
commands that could be used to find previous trace frames....
Stan
next prev parent reply other threads:[~2010-03-17 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 1:59 Stan Shebs
2010-03-17 13:51 ` Marc Khouzam
2010-03-17 15:19 ` Joel Brobecker
2010-03-17 17:36 ` Michael Snyder
2010-03-17 23:40 ` Stan Shebs
2010-03-17 23:44 ` Pedro Alves
2010-03-17 15:22 ` Pedro Alves
2010-03-17 17:31 ` Stan Shebs [this message]
2010-03-18 0:59 ` Stan Shebs
2010-03-18 12:19 ` Pedro Alves
2010-03-18 13:23 ` Pedro Alves
2010-03-18 16:05 ` Tom Tromey
2010-03-18 17:47 ` 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=4BA111CB.3050000@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--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