Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Linux: Use kill_lwp/tkill instead of kill when killing a, process
Date: Tue, 15 Jul 2014 19:33:00 -0000	[thread overview]
Message-ID: <20140715192749.GA32218@host2.jankratochvil.net> (raw)
In-Reply-To: <53C54C7C.3070907@redhat.com>

On Tue, 15 Jul 2014 17:45:00 +0200, Pedro Alves wrote:
> Another thing I noticed by inspection while fixing the
> recent gdbserver kill crash.
> 
> Anyone know a reason we use plain "kill" here, instead
> of tkill like everywhere else?

I do not.
Just it is the general GDB rule of "If it ain't broken, don't fix it".
There are various old and patched kernels out there.


Jan


  reply	other threads:[~2014-07-15 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 15:55 Pedro Alves
2014-07-15 19:33 ` Jan Kratochvil [this message]
2014-07-15 21:03   ` Stan Shebs
2014-07-16 21:58     ` Pedro Alves

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=20140715192749.GA32218@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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