Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: gdb@sourceware.org
Subject: check for valid location of zero length dwarf block forms?
Date: Sun, 22 Nov 2009 17:04:00 -0000	[thread overview]
Message-ID: <20091121034258.GA6166@bromo.med.uc.edu> (raw)

   Since the var-tracking-association code merge into
gcc trunk, we have had issues with Apple's dsymutil
program crashing on the code generated by the FSF
gcc trunk compiler...

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

Apple's dsymutil maintainer analyzed this issue...

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41473#c27
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41473#c29

...as dwarf debug info containing an AT_location with
any block form having a zero length.
   The question is if these emitted dwarf codes are
accidental errors. Apple believes that if the variable
doesn't have a location, the DW_AT_location attribute
shouldn't be emitted. Also, if the variable does have
a valid location, then the length of zero is likely
a bug in dwarf2out.c.
   It might be worthwhile for the gdb developers to
look into this issue since there might be either
unnecessary dwarf output or incorrect dwarf output
that binutils doesn't recognize as such.
     Thanks in advance for any comments.
                 Jack


             reply	other threads:[~2009-11-21  3:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 17:04 Jack Howarth [this message]
2009-11-22 20:22 ` Jan Kratochvil
2009-11-23 14:17   ` Jack Howarth
2009-11-23 19:57     ` Jan Kratochvil
2009-11-24  8:56       ` Jack Howarth
2009-11-24 19:15         ` Cary Coutant

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=20091121034258.GA6166@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=gdb@sourceware.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