From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: filtering of commands during async operation
Date: Fri, 07 Nov 2003 16:14:00 -0000 [thread overview]
Message-ID: <20031107161445.GB29307@nevyn.them.org> (raw)
In-Reply-To: <F56FBA314E8E5A41895F0DA8F6716A6D02A1E3@EMSS04M11.us.lmco.com>
On Fri, Nov 07, 2003 at 11:00:20AM -0500, Newman, Mark (N-Superior Technical Resource Inc) wrote:
>
>
> > From: Elena Zannoni [mailto:ezannoni@redhat.com]
> .....
> >
> > > Next a request - Could you add "tfind", "tdump", "tstart",
> > and "tstop"
> > > to the list of acceptable commands? I know that if I am using
> > > tracepoints to monitor what is going on in a system I
> > don't want to wait
> > > and hope that whatever event I am monitoring for occurs.
> > I want to be
> > > able to look at the tracepoints while they are occurring.
> > >
> >
> >
> > It sounds like a sensible change, however I'd like to know a bit more
> > about the direction you are headed. Surely such a change would be a
> > candidate for a patch.
> >
>
> I am not certain what you mean by where I am headed. My near term
> objective is to get tracepoints running in the background and to provide
> some additions that I typically put in a debugger.
>
> I added some support for tracepoints in gdbserver. I then tested that
> in the foreground. It seemed that everyone writing to the lists at the
> time was doing that. That resulted in couple (3) of bug finds that were
> fixed.
>
> I provided a patch and a bug report (actually an enhancement - which I
> cannot find now) that allows tracepoints to run while in async mode. I
> am now looking at running tracepoints in the background. That resulted
> in this thread.
>
> I am headed at getting tracepoints to the point where I can start a
> remote target running, establish tracepoints, and then go in and peek
> and poke through those tracepoints without disturbing the remote process
> (as Jim's and Michael's Heisenberg paper talked about). I am trying to
> go a step further than their paper by allowing one to inspect the
> tracepoints while the remote is running, collecting, and hopefully not
> being perturbed. This is something I have done in the past with some
> commercial debuggers and I am tired of doing and redoing it.
Hi Mark,
Are you planning to also contribute the gdbserver support for these
feature? I'd love to see it added.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-11-07 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 16:00 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-07 16:14 ` Daniel Jacobowitz [this message]
2003-11-07 17:03 ` Elena Zannoni
[not found] <1068129153.32379.ezmlm@sources.redhat.com>
2003-11-06 17:38 ` Jim Ingham
2003-11-06 19:41 ` Elena Zannoni
2003-11-06 21:16 ` Jim Ingham
2003-11-06 22:10 ` Andrew Cagney
2003-11-06 22:29 ` Elena Zannoni
2003-11-06 22:26 ` Elena Zannoni
-- strict thread matches above, loose matches on Subject: below --
2003-11-06 14:32 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-06 16:57 ` Elena Zannoni
2003-11-05 21:11 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-05 21:52 ` Doug Evans
2003-11-05 22:00 ` Grant Edwards
2003-11-05 22:10 ` Paul Koning
2003-11-05 23:11 ` Elena Zannoni
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=20031107161445.GB29307@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.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