From: Joel Brobecker <brobecker@adacore.com>
To: Andrew D'Addesio <modchipv12@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Process record: Fix null deref when loading empty core file
Date: Thu, 31 May 2018 00:20:00 -0000 [thread overview]
Message-ID: <20180530232553.2diy23kusfrptzdd@adacore.com> (raw)
In-Reply-To: <CANcDefUALe2e7AUq=Q93X5uQcSfzGZ6=X8+aTV8kCxA7nvMwkg@mail.gmail.com>
Hi Andrew,
The patch you sent seems reasonable to me, and I'd be ready to
approve it. But the information you sent below is extremely useful
for understanding the conditions necessary to reproduce the issue
you are fixing. This is both useful for understanding and reviewing
your patch, but also for others who might either find this thread,
or else be looking at your patch, and wondering what you were trying
to do, when you made your change.
With that in mind, can you create a commit which contains the
explanation you just gave in the revision log, followed by whatever
explanation you feel is necessary to provide as to how you fixed
the problem, followed by the ChangeLog entry and a note of how
the fix was tested (which platform, which tests that were a FAIL
now became a PASS).
Browsing the gdb-patches mailing-list for example of how others
submit patches should give you a fair idea of what we prefer.
Do not hesitate to Cc: me on the resubmission of this specific patch,
and I will make every effort to review promptly.
Thank you!
On Fri, May 11, 2018 at 05:00:29PM -0500, Andrew D'Addesio wrote:
> Here's an explanation of the bug:
>
> Description:
[snip]
--
Joel
prev parent reply other threads:[~2018-05-30 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 3:53 Andrew D'Addesio
2018-05-12 6:07 ` Andrew D'Addesio
2018-05-31 0:20 ` Joel Brobecker [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=20180530232553.2diy23kusfrptzdd@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=modchipv12@gmail.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