From: "Eli Zaretskii" <eliz@elta.co.il>
To: Andrew Cagney <ac131313@redhat.com>
Cc: pes@india.hp.com, jimb@redhat.com, gdb@sources.redhat.com
Subject: Re: Tracepoint support in Cygnus GDB ?
Date: Sat, 27 Sep 2003 15:46:00 -0000 [thread overview]
Message-ID: <6654-Sat27Sep2003132618+0300-eliz@elta.co.il> (raw)
In-Reply-To: <3F72FF8C.3080104@redhat.com> (message from Andrew Cagney on Thu, 25 Sep 2003 10:45:32 -0400)
> Date: Thu, 25 Sep 2003 10:45:32 -0400
> From: Andrew Cagney <ac131313@redhat.com>
>
> > "Eli Zaretskii" <eliz@elta.co.il> writes:
> >
> >> > Date: Wed, 24 Sep 2003 16:09:49 +0530
> >> > From: Saravanan <pes@india.hp.com>
> >> >
> >> > 1. Why does GDB not provide this support for local
> >> > host ?
> >
> >>
> >> Simple: because no one wrote tracepoints support for native
> >> debugging.
> >
> >
> > Right -- please contribute support for native tracepoints!
>
> Just don't take Jim's request at face value :-)
On the contrary: please do ;-)
Seriously: as someone who earns his paycheck by writing and debugging
real-time software and teaching others to do so efficiently, a
debugger that can be used to run a real-time program without
completely disrupting it is something to kill for. (Currently, use of
a debugger is limited to coredumps.) If GDB were to support such a
feature, it would be a debugger of choice for many of my co-workers.
If done well, native tracepoints might make this possible.
> The thing to keep in mind is that GDB's development model is one of
> constant incremental change - fix a structure here, move a method there,
> oops just accidently fixed a 15 year old bug of not being able to return
> small structs, ...
If this is supposed to be a gripe on the fact that no significant
user-level changes were added to GDB (except, perhaps, on GNU/Linux
systems), then I, too, am worried by that.
next prev parent reply other threads:[~2003-09-27 10:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 10:40 Saravanan
2003-09-24 18:12 ` Eli Zaretskii
2003-09-24 22:41 ` Jim Blandy
2003-09-25 4:02 ` Daniel Jacobowitz
2003-09-25 21:44 ` Andrew Cagney
2003-09-27 15:46 ` Eli Zaretskii [this message]
2003-09-27 17:49 ` Andrew Cagney
2003-09-27 18:37 ` Eli Zaretskii
2003-09-27 18:48 ` Andrew Cagney
2003-09-28 8:40 ` Eli Zaretskii
2003-09-28 19:44 ` Andrew Cagney
2003-09-28 21:07 ` Eli Zaretskii
2003-09-28 21:30 ` Daniel Jacobowitz
2003-09-29 5:36 ` Eli Zaretskii
2003-09-29 14:48 ` Daniel Jacobowitz
2003-09-28 22:25 ` Andrew Cagney
2003-09-29 5:41 ` Eli Zaretskii
2003-09-29 14:52 ` Andrew Cagney
2003-09-29 15:07 ` Daniel Jacobowitz
2003-10-01 21:49 ` Features vs infrastructure (was Re: Tracepoint support in Cygnus GDB ?) Stan Shebs
2003-10-02 3:29 ` Andrew Cagney
2003-10-02 3:47 ` Stan Shebs
2003-10-02 5:31 ` Andrew Cagney
2003-10-02 6:42 ` Stan Shebs
2003-10-02 7:02 ` Joel Brobecker
2003-10-02 19:18 ` Andrew Cagney
2003-10-02 6:04 ` Stan Shebs
2003-10-02 6:29 ` Andrew Cagney
2003-09-30 5:43 ` Tracepoint support in Cygnus GDB ? Jim Blandy
2003-09-30 21:14 ` Andrew Cagney
2003-09-28 22:50 Michael Elizabeth Chastain
2003-09-29 6:28 ` Eli Zaretskii
2003-09-29 13:21 Michael Elizabeth Chastain
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=6654-Sat27Sep2003132618+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.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