Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org, Gary Benson <gbenson@redhat.com>
Subject: Re: ping: [PATCH 1/3] Never kill PID on: gdb exec PID
Date: Thu, 14 Apr 2016 17:24:00 -0000	[thread overview]
Message-ID: <20160414172353.GA29418@host1.jankratochvil.net> (raw)
In-Reply-To: <570FC823.7020908@codesourcery.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


      reply	other threads:[~2016-04-14 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 15:44 Jan Kratochvil
2016-04-14 16:41 ` Luis Machado
2016-04-14 17:24   ` Jan Kratochvil [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=20160414172353.GA29418@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.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