From: Alexander Shaposhnikov <alexander.v.shaposhnikov@gmail.com>
To: Nathan Sidwell <nathan@acm.org>, Doug Evans <dje@google.com>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [gdb patch] seg fault on missing dwarf
Date: Tue, 26 Sep 2017 23:12:00 -0000 [thread overview]
Message-ID: <CAFG51+=eu8PU=imBdK-JDkD6iNbZjJifgiM_iKHWeTvR_i9ZRg@mail.gmail.com> (raw)
In-Reply-To: <a69a38b4-f3a9-4dce-382f-4ca34150f988@acm.org>
Many thanks to everyone for looking at my patch,
i sent the final version (updated following Doug Evans suggestion) this
morning
https://sourceware.org/ml/gdb-patches/2017-09/msg00814.html
- so yeah, i would be very grateful if smb could commit this for me.
Regarding the separate issue with the dependence on the order of sections
(unrelated to this patch) - i'm currently preparing a bug report - will
file it to bugzilla soon.
Kind regards,
Alexander Shaposhnikov
On Tue, Sep 26, 2017 at 4:05 PM, Nathan Sidwell <nathan@acm.org> wrote:
> On 09/26/2017 07:27 AM, Pedro Alves wrote:
>
>> 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
>>
>
> Ah, I see the state changed between me checking and actually sending email
> :) Alex, do you need me to commit this on your behalf?
>
> nathan
>
> --
> Nathan Sidwell
>
prev parent reply other threads:[~2017-09-26 23:12 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
2017-09-26 23:05 ` Nathan Sidwell
2017-09-26 23:12 ` Alexander Shaposhnikov [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='CAFG51+=eu8PU=imBdK-JDkD6iNbZjJifgiM_iKHWeTvR_i9ZRg@mail.gmail.com' \
--to=alexander.v.shaposhnikov@gmail.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=nathan@acm.org \
--cc=palves@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