Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jimb@red-bean.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] Deal with -g1 generated DWARF2 debug info
Date: Mon, 05 Dec 2005 16:56:00 -0000	[thread overview]
Message-ID: <200512042230.jB4MUmMw002961@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <8f2776cb0512041400x257a1889u8fb53eb23e62ce49@mail.gmail.com> 	(message from Jim Blandy on Sun, 4 Dec 2005 14:00:21 -0800)

> Date: Sun, 4 Dec 2005 14:00:21 -0800
> From: Jim Blandy <jimb@red-bean.com>
>
> The central issue here is that the compiler is emitting incorrect
> debug info.  The GCC manual says of -g1:
> 
>      Level 1 produces minimal information, enough for making backtraces
>      in parts of the program that you don't plan to debug.  This
>      includes descriptions of functions and external variables, but no
>      information about local variables and no line numbers.
> 
> Nothing there about reducing all return types to 'void'.

But fixing that would probably require that GCC dumps the complete
type info, which would reduce the usefulness of -g1.  And that doesn't
change the fact that GCC probably has been doing this for quite some
time now.


  parent reply	other threads:[~2005-12-04 22:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04 22:05 Mark Kettenis
2005-12-04 22:31 ` Jim Blandy
2005-12-05  9:43   ` Mark Kettenis
2005-12-04 22:40 ` Jim Blandy
2005-12-04 23:06   ` Daniel Jacobowitz
2005-12-04 23:07     ` Jim Blandy
2005-12-05 10:32       ` Daniel Jacobowitz
2005-12-05 18:29         ` Mark Kettenis
2005-12-05 19:23           ` Daniel Jacobowitz
2005-12-07 16:19             ` Mark Kettenis
2005-12-05 16:56       ` Mark Kettenis [this message]
2005-12-05 19:57         ` Daniel Jacobowitz
2005-12-05 14:40   ` Mark Kettenis

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=200512042230.jB4MUmMw002961@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.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