Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: ac131313@redhat.com,gdb@sources.redhat.com
Subject: Re: Tracepoint support in Cygnus GDB ?
Date: Mon, 29 Sep 2003 05:36:00 -0000	[thread overview]
Message-ID: <u1xu0i0ib.fsf@elta.co.il> (raw)
In-Reply-To: <20030928210701.GA22100@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 28 Sep 2003 17:07:01 -0400)

> Date: Sun, 28 Sep 2003 17:07:01 -0400
> From: Daniel Jacobowitz <drow@mvista.com>
> 
> On Sun, Sep 28, 2003 at 11:41:20PM +0200, Eli Zaretskii wrote:
> > > Separate debug info is very much an embedded feature - it lets embedded 
> > > distros make optional all the debug info for all those embedded C and 
> > > C++ libraries.
> > 
> > Still, it requires a feature in Binutils that only exists on
> > GNU/Linux.
> 
> That is not correct.  It works for any ELF target.

Perhaps I don't know something: I thought that separate debug info
required support from Binutils, to be able to produce the files with
the debug info.  I'm sure at some point someone said here that this
option is not available on all systems.  Isn't that right?  What is
the exact procedure of producing the separate debug info?

> Don't you consider improved debugging of optimized code to be
> a feature?  Especially considering how abysmal support is now.

I consider this a bugfix.


  reply	other threads:[~2003-09-29  5:18 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
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 [this message]
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=u1xu0i0ib.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=ac131313@redhat.com \
    --cc=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