Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch 2/3] attach-fail-reasons: Say more than ptrace: Operation not permitted.
Date: Tue, 13 Mar 2012 14:35:00 -0000	[thread overview]
Message-ID: <4F5F5B0F.8010804@redhat.com> (raw)
In-Reply-To: <20120313135457.GA8363@host2.jankratochvil.net>

On 03/13/2012 01:54 PM, Jan Kratochvil wrote:

> On Tue, 13 Mar 2012 11:33:19 +0100, Pedro Alves wrote:
>> On 03/13/2012 09:43 AM, Jan Kratochvil wrote:
>>> I agree, this is affecting all the /proc operations.  
> 
> OK, so not completely all.
> 
> 
>> Yeah, although if you're already attached to the process, then the risk of /proc/..
>> hitting the wrong pid is much lower, though it does exist.
> 
> How?  It remains as 'Z (zombie)' with non-zero 'TracerPid' and even root
> cannot reuse that PID without killing the tracer.


E.g., with a multi-threaded exec, the execing thread just disappears
from /proc/TID as in reality the kernel changed the execing thread's TID, so
it's possible we end trying to open the non-existing /proc/TID/... before handling
the exec event.  I think there were other ways for a tracee to be completely
killed/removed behind the tracer's back, but maybe that was only with older kernels,
if it ever was.

>>>   (2b) If introducing a new framework to gdbserver code we should bring in STL
>>>        and not the libiberty/gdb code.  But we cannot yet use STL.
>>
>> Although I'm a C++ supporter, I really don't think such C++ arguments hold
>> much weight for the current C based code base.
> 
> Offtopic here but I think this code was another argument for C++, wasn't it?


It was like saying that if you had posted this code written in C++ doing this
dynamic string growth with delete[]/new[] to reallocate (instead of std::string, not
knowing its existence), and justified it by claiming the right solution is to
switch to Java.   Eventually.  And only maybe.

> gdb/
> 2012-03-13  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* common/linux-procfs.c (linux_proc_get_int): New, from
> 	linux_proc_get_tgid, change its LWPID type to pid_t, add parameter
> 	field.
> 	(linux_proc_get_tgid): Only call linux_proc_get_int.
> 	(linux_proc_get_tracerpid): New.
> 	(linux_proc_pid_has_state): New, from linux_proc_pid_is_zombie.
> 	(linux_proc_pid_is_stopped, linux_proc_pid_is_zombie): Only call
> 	linux_proc_pid_has_state.
> 	* common/linux-procfs.h (linux_proc_get_tracerpid): New declaration.
> 	* common/linux-ptrace.c: Include linux-procfs.h and buffer.h.
> 	(linux_ptrace_attach_warnings): New.
> 	* common/linux-ptrace.h (struct buffer, linux_ptrace_attach_warnings):
> 	New declaration.
> 	* linux-nat.c: Include exceptions.h, linux-ptrace.h and buffer.h.
> 	(linux_nat_attach): New variables ex, buffer, message and message_s.
> 	Wrap to_attach by TRY_CATCH and call linux_ptrace_attach_warnings.
> 
> gdb/gdbserver/
> 2012-03-13  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* linux-low.c (linux_attach_lwp_1): New variable buffer.  Call
> 	linux_ptrace_attach_warnings.
> 
> gdb/testsuite/
> 2012-03-06  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* gdb.base/attach-twice.c: New files.
> 	* gdb.base/attach-twice.exp: New files.
> 


Looks good too.

-- 
Pedro Alves


  reply	other threads:[~2012-03-13 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  6:17 Jan Kratochvil
2012-03-08 13:55 ` Pedro Alves
2012-03-13  9:43   ` Jan Kratochvil
2012-03-13 10:33     ` Pedro Alves
2012-03-13 13:55       ` Jan Kratochvil
2012-03-13 14:35         ` Pedro Alves [this message]
2012-03-13 14:50           ` Jan Kratochvil
2012-03-13 15:03           ` [commit] " Jan Kratochvil
2012-03-14 15:12         ` Tom Tromey

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=4F5F5B0F.8010804@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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