From: Stan Shebs <stan@codesourcery.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Stan Shebs <stan@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Observer mode
Date: Fri, 30 Apr 2010 03:19:00 -0000 [thread overview]
Message-ID: <4BDA4C34.1010708@codesourcery.com> (raw)
In-Reply-To: <4BD9CC1D.9040104@vmware.com>
Michael Snyder wrote:
> Stan Shebs wrote:
>> Here is another patch that pushes the envelope a bit, and for which I
>> would like to get some prior agreement that it's a good idea.
>>
>> The basic idea here is that GDB is to be used to look at targets
>> installed in the field and in use. In such a situation it may
>> connect to the target and examine state, but not alter that state or
>> interrupt anything. In our particular target, tracing is allowed,
>> but only using fast tracepoints, because they are done using jumps
>> and thus act as if they were part of the program; taking a trap, even
>> for a slow tracepoint, disrupts thread execution unacceptably. We
>> have been calling this "observer mode", and the customer's GDB is
>> actually configured to launch in this mode, to reduce the chance of
>> accidental stopping - the debugger user has to ask specifically to
>> change it to normal debugging mode.
>>
>> [...]
>
> How different is this from async mode?
Observer mode includes async mode. One could call it a "read-only
non-stop async mode that allows fast tracepoints", although that's
rather a mouthful. :-)
Stan
next prev parent reply other threads:[~2010-04-30 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 17:23 Stan Shebs
2010-04-29 17:54 ` Eli Zaretskii
2010-04-29 18:12 ` Michael Snyder
2010-04-30 3:19 ` Stan Shebs [this message]
2010-04-30 18:21 ` Tom Tromey
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=4BDA4C34.1010708@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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