From: Simon Marchi <simon.marchi@polymtl.ca>
To: Mike Gulick <mgulick@mathworks.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
Mike Gulick <mike.gulick@mathworks.com>,
gdb-patches@sourceware.org
Subject: Re: [RFC][PATCH] fix gdb segv when objfile can't be opened
Date: Mon, 08 Jan 2018 02:51:00 -0000 [thread overview]
Message-ID: <991575a07a4614be2c9aa5aa6dcf2ea7@polymtl.ca> (raw)
In-Reply-To: <aca01354700f3d63d52720eefc984364@polymtl.ca>
On 2018-01-07 21:50, Simon Marchi wrote:
> On 2018-01-07 19:44, Mike Gulick wrote:
>> Hi Simon,
>>
>> I submitted the assignment paperwork to the FSF on December 19th. I
>> have not
>> heard back yet, but I will send a follow up email to make sure there
>> are no
>> issues. Sorry for the delay.
>>
>> -Mike
>
> Ok, no problem. I still have the shlib patch in queue for when you'll
> be ready to push.
>
> Simon
Sorry that wasn't clear, I meant the testsuite shlib= patch.
Simon
next prev parent reply other threads:[~2018-01-08 2:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 14:10 Mike Gulick
2017-10-19 15:59 ` Mike Gulick
2017-10-19 17:54 ` Simon Marchi
2017-10-19 19:39 ` Mike Gulick
2017-10-19 20:10 ` Simon Marchi
2017-10-19 22:13 ` Mike Gulick
2017-10-23 23:19 ` Mike Gulick
2017-10-27 21:11 ` Simon Marchi
2017-10-28 1:19 ` Simon Marchi
2017-10-30 22:14 ` Mike Gulick
2017-10-30 23:38 ` Simon Marchi
2018-01-07 14:09 ` Simon Marchi
2018-01-08 0:45 ` Mike Gulick
2018-01-08 2:50 ` Simon Marchi
2018-01-08 2:51 ` Simon Marchi [this message]
2018-01-10 20:33 ` Mike Gulick
2018-01-12 2:44 ` Simon Marchi
2018-01-12 15:05 ` Mike Gulick
2018-01-17 18:01 ` Simon Marchi
2018-01-18 15:30 ` Mike Gulick
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=991575a07a4614be2c9aa5aa6dcf2ea7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=mgulick@mathworks.com \
--cc=mike.gulick@mathworks.com \
--cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).