This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: ping: [PATCH 1/3] Never kill PID on: gdb exec PID
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Luis Machado <lgustavo at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org, Gary Benson <gbenson at redhat dot com>
- Date: Thu, 14 Apr 2016 19:23:53 +0200
- Subject: Re: ping: [PATCH 1/3] Never kill PID on: gdb exec PID
- Authentication-results: sourceware.org; auth=none
- References: <20160414154439 dot GA1489 at host1 dot jankratochvil dot net> <570FC823 dot 7020908 at codesourcery dot com>
On Thu, 14 Apr 2016 18:41:07 +0200, Luis Machado wrote:
> On 04/14/2016 10:44 AM, Jan Kratochvil wrote:
> >It would be nice to upstream at least this fix of the series:
> > Subject: [PATCH 1/3] Never kill PID on: gdb exec PID
> > Message-ID: <20151016204733.27288.56498.stgit@host1.jankratochvil.net>
> > https://sourceware.org/ml/gdb-patches/2015-10/msg00301.html
>
> Is this still happening after 57d1de9cf3ba8dd98eaf4a3d131c05ec4c49779d?
>
> I couldn't reproduce what you saw with master GDB.
The new testcase of mine has been fixed in the meantime by:
bf74e428bca61022bd5cdf6bf28789a184748b4d is the first bad (=good) commit
commit bf74e428bca61022bd5cdf6bf28789a184748b4d
Author: Gary Benson <gbenson@redhat.com>
Date: Wed Feb 24 11:31:58 2016 +0000
Fix logic in exec_file_locate_attach
So the bug is probably fixed; I still find the logic in my patch correct as
some safety whether to run core_file_command() or not but I will no longer
ping the patch in the future.
Thanks,
Jan