Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC PATCH] Introduce dwarf2_cu::get_builder
Date: Fri, 30 Nov 2018 20:30:00 -0000	[thread overview]
Message-ID: <87a7lqmhpg.fsf@tromey.com> (raw)
In-Reply-To: <20181023185715.23082-1-keiths@redhat.com> (Keith Seitz's message	of "Tue, 23 Oct 2018 11:57:15 -0700")

>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:

Keith> This patch is an attempt to deal with a variety of bugs reported where
Keith> GDB segfaults attempting to access a dwarf2_cu's builder.  In certain
Keith> circumstances, this builder can be NULL.

I think it would be good to describe one such case in the commit
message.  I suppose there must be some spot that works on an inherited
DIE in the context of its own CU?  I found myself wondering where.

Keith> I'm submitting this as an RFC rather than an actual patch because of the
Keith> lack of coverage testing for all the places where get_builder() is used.

I wouldn't be surprised if some of them aren't really reachable in the
sense of ever being able to take the ancestor path.  I'm not concerned
about needing tests for every single point.

Keith> +# This tests a segfault that occurs when reading inline_subroutine DIEs

inlined_subroutine (missing the "d")

Keith> +# bugzila mentioned above.  For clarity, some "superfluous" DIES have

Missing an "l" in bugzilla.

The rest seems good to me.  Thank you for the patch, and for reducing
and rewriting the test case like this.

Tom


  parent reply	other threads:[~2018-11-30 20:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 18:57 Keith Seitz
2018-10-23 19:41 ` Sergio Durigan Junior
2018-11-06 21:34 ` Keith Seitz
2018-11-14 16:20   ` Keith Seitz
2018-11-16 13:19 ` Simon Marchi
2018-11-16 14:39   ` Keith Seitz
2018-11-30 20:30 ` Tom Tromey [this message]
2019-01-08 19:56   ` Keith Seitz
2019-01-16 16:38     ` Tom Tromey

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=87a7lqmhpg.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.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