Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Tom Tromey <tom@tromey.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 8.2 released!
Date: Sun, 09 Sep 2018 20:25:00 -0000	[thread overview]
Message-ID: <20180909202550.GB40953@wildebeest.org> (raw)
In-Reply-To: <87in3e4iwz.fsf@tromey.com>

On Sun, Sep 09, 2018 at 12:36:44PM -0600, Tom Tromey wrote:
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> CCing Mark Wielaard -- Mark see about 3/4 down...

Hi Tom,

> Eli>    During symbol reading, cannot get low and high bounds for subprogram DIE at 0x40c43e.
> 
> Eli>    During symbol reading, Child DIE 0x4433a0 and its abstract origin 0x448aff have different parents.
> 
> Eli>    During symbol reading, No DW_FORM_block* DW_AT_call_value for DW_TAG_call_site child DIE 0x447010 [in module D:\gnu\gdb-8.2\gdb\gdb.exe].
> 
> Eli>    During symbol reading, Multiple children of DIE 0x448d3a refer to DIE 0x448a80 as their abstract origin.
> 
> Eli>    During symbol reading, DIE 0x44aa21 and its abstract origin 0x446e69 have different tags.
> 
> I don't know about these.
> Many times these complaints are due to DWARF oddities, but I feel there
> are some complaints that represent gdb limitations.  So you have to dig
> to find out.
> 
> I think most of these things would be good things for dwarflint to
> check.  (Hi Mark.)

Yes, they would be. But... eu-dwarflint really needs a bit of help.
It is only available on a branch:
https://sourceware.org/git/?p=elfutils.git;a=shortlog;h=refs/heads/dwarflint
No other code is written in C++. To get it integrated into master it
would need someone with some knowledge of C++ and what good interfaces
are that are easy to keep API compatible in the long run. Or it would
need someone with some build/auto* knowledge to get it to build
completely on the build of dwarflint itself can easily be disabled.

Cheers,

Mark


      parent reply	other threads:[~2018-09-09 20:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <announce.20180905091451.5DEB883A8F@joel.gnat.com>
2018-09-09 10:07 ` Eli Zaretskii
2018-09-09 18:36   ` Tom Tromey
2018-09-09 19:24     ` Eli Zaretskii
2018-09-09 19:45       ` Tom Tromey
2018-09-09 19:49       ` Eli Zaretskii
2018-09-10  1:41         ` Tom Tromey
2018-09-10  7:16           ` Eli Zaretskii
2018-09-10 16:01             ` Tom Tromey
2018-09-10 17:29               ` Eli Zaretskii
2018-09-09 20:25     ` Mark Wielaard [this message]

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=20180909202550.GB40953@wildebeest.org \
    --to=mark@klomp.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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