Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Nathan Sidwell <nathan@acm.org>, gdb-patches@sourceware.org
Cc: alexander.v.shaposhnikov@gmail.com
Subject: Re: [gdb patch] seg fault on missing dwarf
Date: Tue, 26 Sep 2017 14:27:00 -0000	[thread overview]
Message-ID: <bf713c1a-a989-5372-1b84-99e6c6ee5f2c@redhat.com> (raw)
In-Reply-To: <02efda56-3678-f4f6-849d-df474214e82f@acm.org>

Hi Nathan,

On 09/25/2017 09:33 PM, Nathan Sidwell wrote:
> Pedro,
> this is Alex's patch of
> https://sourceware.org/ml/gdb-patches/2017-09/msg00745.html cleaned up
> with changelog formatting.  Alex is a fellow FaceBooker.

FYI, Doug reviewed Alex's patch:
  https://sourceware.org/ml/gdb-patches/2017-09/msg00779.html

Thanks,
Pedro Alves


  reply	other threads:[~2017-09-26 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 20:33 Nathan Sidwell
2017-09-26 14:27 ` Pedro Alves [this message]
2017-09-26 23:05   ` Nathan Sidwell
2017-09-26 23:12     ` 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=bf713c1a-a989-5372-1b84-99e6c6ee5f2c@redhat.com \
    --to=palves@redhat.com \
    --cc=alexander.v.shaposhnikov@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nathan@acm.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