public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Newman, Mark (N-Superior Technical Resource Inc)" <mark.newman@lmco.com>
To: Saravanan <pes@india.hp.com>
Cc: jimb@redhat.com, Johnson Samuel <johns@india.hp.com>,
	gdb@sources.redhat.com
Subject: RE: tracepoints
Date: Thu, 02 Oct 2003 14:20:00 -0000	[thread overview]
Message-ID: <F56FBA314E8E5A41895F0DA8F6716A6D02A1BE@EMSS04M11.us.lmco.com> (raw)


Hi Saravan -

Lockheed does not use HP-GDB.  However in the past something very much
like tracepoints has been used as part of the integration of large
systems.  That was done at enormous cost.  I am looking at a low cost
mechanism for doing it in the future.  (I wrote the earlier
implementations and have written a current gdb/gdbserver
implementation).

I don't understand the desire to have tracepoints in a native
environment.  Tracepoints are designed to be non(read
minimally)-invasive.  They are designed to be sensitive to Heisenberg.
That means that they perturb system operation as little as possible
while collecting data. 

When we have used this type of functionality the idea was to set up a
situation, collect information, wait for some event to occur, and then
go in and look and see what happened.  That event may or may not be a
planned event.  It was used less to debug programs and more to debug
systems.  It was an integration tool (although it has been used to debug
logic problems) that allows one to see what happens in the dirty
environment of the real world.  Not in the clean environment of a test
case.

The only real differences I see between what we used in the past and
Introspect is the fact that Introspect collects data in the target
memory and the target is halted when the data is being analyzed.  The
former means to me that if I am not careful the data can have rolled off
the end of a queue before I look at it or perhaps the target locked and
I can't get at the collected data.  The latter violates the principle
espoused by Heisenberg.

Please let me know what your feelings are.  This idea has been cobbed
together by a relatively small group of people in the past.  It needs to
have the scrutiny of many talented people applied to it.

                                              Mark Newman  


-----Original Message-----
From: Saravanan [mailto:pes@india.hp.com]
Sent: Wednesday, October 01, 2003 7:34 AM
To: Newman, Mark (N-Superior Technical Resource Inc)
Cc: jimb@redhat.com; Johnson Samuel
Subject: Re: tracepoints


Hi ,
   I am Saravanan working for supporting HP-GDB/WDB product. I am doing
a feasibility
study of supporting native tracepoints in HP-GDB/WDB. 

  Does Lockheed use HP-GDB/WDB for their debugging? If yes, would it
help if we put this
feature in HP-GDB/WDB ?

Regards,
Saravanan

> 
> Saravanan
> 
> Lockheed is investing money in tracepoints.  I have not been able to
get on the GDB mailing list's to indicate our interest in supporting
them although I have spent time discussing an implementation with people
at Redhat.
> 
> If you would like to work towards a common goal please let me know
> 
>
Mark Newman

             reply	other threads:[~2003-10-02 14:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02 14:20 Newman, Mark (N-Superior Technical Resource Inc) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-23 13:49 tracepoints Maxim Osipov
2006-01-23 15:00 ` tracepoints Daniel Jacobowitz
2006-01-23 15:20   ` tracepoints Maxim Osipov
2006-01-23 19:37 ` tracepoints Jim Blandy
2003-10-07 13:00 Tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-07 16:33 ` Tracepoints Jim Blandy
2003-10-08 17:21 ` Tracepoints Andrew Cagney
2003-10-06 13:39 Tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-06 21:03 ` Tracepoints Jim Blandy
2003-10-02 13:16 Tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-02 19:23 ` Tracepoints Andrew Cagney
2001-07-11 10:38 Tracepoints Billalabeitia, Jose Carlos (IndSys, GEPM)
2001-03-21 15:59 tracepoints Edward Peschko
2001-03-21 15:59 ` tracepoints Eli Zaretskii
2001-03-21 15:59 tracepoints Nicolas.Thery
2001-03-21 15:59 ` tracepoints Edward Peschko
2001-03-21 15:59   ` tracepoints Eli Zaretskii
2001-03-21 15:59 ` tracepoints Eli Zaretskii
2001-03-21 15:59   ` tracepoints Eli Zaretskii
2001-02-27 19:50 tracepoints Edward Peschko

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=F56FBA314E8E5A41895F0DA8F6716A6D02A1BE@EMSS04M11.us.lmco.com \
    --to=mark.newman@lmco.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=johns@india.hp.com \
    --cc=pes@india.hp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).