Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@www.cgsoftware.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: <gdb@sources.redhat.com>
Subject: Re: Cast to a struct in expressions
Date: Sat, 28 Apr 2001 23:52:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0104290248390.17968-100000@www.cgsoftware.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010429094849.26520F@is>

On Sun, 29 Apr 2001, Eli Zaretskii wrote:

>
> On Sat, 28 Apr 2001, Daniel Berlin wrote:
>
> > I have to modify that part of the docs since it says stabs is good for C++
> > (which hasn't been true for about 4 years now) anyway
>
> Well, it only says ``for best results [...] use -gstabs'', so it's not
> an absolute.
Best results will happen with dwarf2, not stabs.

> Stabs are certainly better than, say, COFF debug info
> for debugging C++.  And if GCC is used, stabs are available on more
> platforms than dwarf2.  So I think the manual language isn't totally
> wrong.
Well, it's also only the default on older platforms. I haven't seen a new
port in well over a year that uses STABS as a default.

>
> Btw, if stabs aren't the best type of debug info available in GDB 5.0 for
> debugging C++ code, what is?
>
dwarf2.
By a large margin.

Especially if you call functions.
Overload resolution, for instance, on STABS, is basically a complete hack.
Okay, not basically, it flat out is.
--Dan


  reply	other threads:[~2001-04-28 23:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27  1:10 Eli Zaretskii
2001-04-27  8:24 ` Daniel Berlin
2001-04-27 10:41   ` Eli Zaretskii
2001-04-27 12:30     ` Daniel Berlin
2001-04-28  1:08       ` Eli Zaretskii
2001-04-28  2:12         ` Paul Hilfinger
2001-04-28 11:30           ` Daniel Berlin
2001-04-28 11:09         ` Daniel Berlin
2001-04-28 23:47           ` Eli Zaretskii
2001-04-28 23:52             ` Daniel Berlin [this message]
2001-04-29  0:20               ` Eli Zaretskii

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=Pine.LNX.4.33.0104290248390.17968-100000@www.cgsoftware.com \
    --to=dan@www.cgsoftware.com \
    --cc=eliz@is.elta.co.il \
    --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