public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/23190] [4.0/4.1 Regression] debug info omitted for uninitialized variables (stabs)
Date: Tue, 02 Aug 2005 03:25:00 -0000	[thread overview]
Message-ID: <20050802032539.32312.qmail@sourceware.org> (raw)
In-Reply-To: <20050802003405.23190.dpatel@apple.com>


------- Additional Comments From mark at codesourcery dot com  2005-08-02 03:25 -------
Subject: Re:  [4.0/4.1 Regression] debug info omitted for
 uninitialized variables (stabs)

pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2005-08-02 00:42 -------
> Actually the PR 21828 was orginally about stabs and not about dwarf-2:
> "When using gdb-309 and gdb-370 on MacOS X 10.3.9, even the simplest queries seem broken." so 
> really PR 21828 should never been closed until the stabs problem was fixed.

Then the test case in the PR (which you provided) should not have used 
DWARF-2.  I rely on the bugmasters to reduce bugs -- and they do a great 
job.

In any case, the problem is now either in the C front end or in the DBX 
generator.  Since the DWARF-2 generators do something reasonable, 
AFAICT, I would guess the problem is in either the DBX generator, or the 
  GDB reader for STABS, or in the STABS format itself.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23190


  parent reply	other threads:[~2005-08-02  3:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02  0:34 [Bug debug/23190] New: debug info omitted for uninitialized variables dpatel at apple dot com
2005-08-02  0:37 ` [Bug debug/23190] [4.0/4.1 Regression] debug info omitted for uninitialized variables (stabs) pinskia at gcc dot gnu dot org
2005-08-02  0:41 ` pinskia at gcc dot gnu dot org
2005-08-02  0:42 ` pinskia at gcc dot gnu dot org
2005-08-02  3:25 ` mark at codesourcery dot com [this message]
2005-08-02 16:52 ` dpatel at apple dot com
2005-08-02 17:01 ` mmitchel at gcc dot gnu dot org
2005-08-02 17:12 ` dpatel at apple dot com
2005-08-02 17:16 ` mark at codesourcery dot com
2005-08-02 17:21 ` dpatel at apple dot com
2005-09-08  2:39 ` rth at gcc dot gnu dot org
2005-09-08  2:42 ` rth at gcc dot gnu dot org
2005-09-09  0:47 ` cvs-commit at gcc dot gnu dot org
2005-09-09  0:52 ` cvs-commit at gcc dot gnu dot org
2005-09-09  1:08 ` rth at gcc dot gnu dot org

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=20050802032539.32312.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).