From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: "Glenn F. Maynard" <g_gdb@zewt.org>
Cc: gdb@sourceware.cygnus.com
Subject: Re: gdb: detection and/or fork+gethostbyname crash workaround?
Date: Tue, 24 Jul 2001 13:26:00 -0000 [thread overview]
Message-ID: <20010724132604.A18052@nevyn.them.org> (raw)
In-Reply-To: <20010724142248.A2923@zewt.org>
On Tue, Jul 24, 2001 at 02:22:48PM -0400, Glenn F. Maynard wrote:
> On Tue, Jul 24, 2001 at 08:52:19AM -0700, Kevin Buettner wrote:
> > If it's one which uses ptrace(), the kernel usually prohibits two
> > processes from invoking ptrace() on the same inferior. So one
> > strategy might be to have the program in question cause ptrace to be
> > invoked on itself. I don't think the process will be able to do this
> > itself; I think it's likely that it would have to fork and let the
> > child attempt this. The return status from wait() or waitpid() could
> > indicate whether the attempt to invoke ptrace() was successful or not.
>
> That's what I tried (x86 Linux); a process can't ptrace itself. I could
> fork a process to test this, I suppose; I'll try that. (Wouldn't it
> be the return status from ptrace(), though? I assume it'd return something
> like EPERM if a process is already being debugged.)
Try ptrace( PTRACE_TRACEME, ...) ?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-07-24 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 18:01 Glenn F. Maynard
2001-07-24 9:23 ` Kevin Buettner
2001-07-24 11:22 ` Glenn F. Maynard
2001-07-24 13:26 ` Kevin Buettner
2001-07-24 13:57 ` Glenn F. Maynard
2001-07-24 14:49 ` Kevin Buettner
2001-07-24 14:22 ` Daniel Jacobowitz
2001-07-24 13:26 ` Daniel Jacobowitz [this message]
2001-07-24 13:44 ` Kevin Buettner
2001-07-24 13:54 ` Mark Kettenis
2001-07-24 13:00 Michael Elizabeth Chastain
2001-07-24 13:53 ` Kevin Buettner
2001-07-24 14:26 ` Glenn F. Maynard
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=20010724132604.A18052@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=g_gdb@zewt.org \
--cc=gdb@sourceware.cygnus.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