Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 8.1.90 available for testing
Date: Thu, 19 Jul 2018 14:48:00 -0000	[thread overview]
Message-ID: <83bmb32sev.fsf@gnu.org> (raw)
In-Reply-To: <87effzi972.fsf@tromey.com> (message from Tom Tromey on Thu, 19	Jul 2018 08:36:33 -0600)

> From: Tom Tromey <tom@tromey.com>
> Cc: Joel Brobecker <brobecker@adacore.com>,  gdb-patches@sourceware.org
> Date: Thu, 19 Jul 2018 08:36:33 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli> Other that that, the build went cleanly.  The new GDB binary, when
> Eli> invoked on itself, reports the following DWARF-related issues:
> 
> Eli>      During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'.
> 
> This is https://sourceware.org/bugzilla/show_bug.cgi?id=17271
> It is probably harmless.
> 
> Eli>      During symbol reading, Member function "~_Sp_counted_base" (offset 0x3ef4f6) is virtual but the vtable offset is not specified.
> 
> This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37237
> It's an ongoing problem with no resolution in sight.  It affects
> gdb users sometimes:
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=15975

Thanks for the pointers.  Truth be told, I'm quite surprised that some
of these are known for 10 years...


  reply	other threads:[~2018-07-19 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04 16:32 Joel Brobecker
2018-07-18 16:13 ` Eli Zaretskii
2018-07-19 14:37   ` Tom Tromey
2018-07-19 14:48     ` Eli Zaretskii [this message]
2018-07-29  2:37   ` Eli Zaretskii
2018-07-29 18:43     ` Tom Tromey
2018-07-31 16:58       ` 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=83bmb32sev.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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