Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Doug Evans via gdb-patches" <gdb-patches@sourceware.org>
To: Alexander Shaposhnikov <alexander.v.shaposhnikov@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix reading .dwp files without .debug_tu_index
Date: Thu, 28 Sep 2017 16:30:00 -0000	[thread overview]
Message-ID: <001a113e2ba0ccc3b4055a426b0b@google.com> (raw)

Alexander Shaposhnikov writes:
 > (updated patch + changelog)
 > 
 > changelog:
 > 
 > 2017-09-26  Alexander Shaposhnikov <alexander.v.shaposhnikov@gmail.com>
 > 	
 > 	* dwarf2read.c (open_and_init_dwp_file): Protect against dwp_file
 > 	having NULL cus or tus.

Thanks! Committed.


             reply	other threads:[~2017-09-28 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 16:30 Doug Evans via gdb-patches [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-19 19:58 Alexander Shaposhnikov
2017-09-24 23:37 ` Alexander Shaposhnikov
2017-09-26  3:15 ` Doug Evans via gdb-patches
2017-09-26  4:13   ` Alexander Shaposhnikov
2017-09-26 17:51     ` Doug Evans via gdb-patches
2017-09-26 18:48       ` Alexander Shaposhnikov

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=001a113e2ba0ccc3b4055a426b0b@google.com \
    --to=gdb-patches@sourceware.org \
    --cc=alexander.v.shaposhnikov@gmail.com \
    --cc=dje@google.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