From: Mike Gulick <mgulick@mathworks.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
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: Fri, 12 Jan 2018 15:05:00 -0000 [thread overview]
Message-ID: <990f8e00-04f1-7823-39fb-fe9d2dfdbebb@mathworks.com> (raw)
In-Reply-To: <0b995e7e758a2d7fb43689c282264870@polymtl.ca>
On 01/11/2018 09:44 PM, Simon Marchi wrote:
> On 2018-01-10 15:33, Mike Gulick wrote:
>> Hi Simon,
>>
>> I received the signed assignment agreement back from the FSF yesterday. I
>> rebased my patches on the current gdb tip and re-ran the test suite, with no
>> unexpected regressions. Should I re-post the patches?
>>
>> Thanks,
>> Mike
>
> Hi Mike,
>
> I don't think reposting the patch is necessary, unless it changed substantially when rebasing.
>
> I suppose you don't have push access to Sourceware yet? If you plan on contributing to GDB regularly, it would be a good idea to get it, see [1] for details. Otherwise I can push the patch for you, it's as you wish.
>
> FYI, I just pushed the patch that fixes the shlib= problem you had:
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=6181e9c2c5ba252ac016f51903dc35d7bfbbca71
>
> Simon
>
> [1] https://sourceware.org/cgi-bin/pdw/ps_form.cgi
Hi Simon,
There weren't any code changes when rebasing. The only changes I have locally
are just updating the changelog dates, and adding the missing tabs in the
changelog section of the commit message. Feel free to push the change already
posted, with any fixups you see as necessary.
Next time I have a change to be submitted, I'll look into getting a Sourceware
account.
Thanks,
Mike
next prev parent reply other threads:[~2018-01-12 15:05 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
2018-01-10 20:33 ` Mike Gulick
2018-01-12 2:44 ` Simon Marchi
2018-01-12 15:05 ` Mike Gulick [this message]
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=990f8e00-04f1-7823-39fb-fe9d2dfdbebb@mathworks.com \
--to=mgulick@mathworks.com \
--cc=gdb-patches@sourceware.org \
--cc=mike.gulick@mathworks.com \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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