From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Mark Kettenis <kettenis@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] Replace call_ptrace and ptrace_wait in inf-ptrace.c
Date: Mon, 20 Sep 2004 19:42:00 -0000 [thread overview]
Message-ID: <20040920194212.GA10736@nevyn.them.org> (raw)
In-Reply-To: <414F30D1.7080706@gnu.org>
On Mon, Sep 20, 2004 at 03:34:41PM -0400, Andrew Cagney wrote:
> >This is another step in the direction of eliminating the need for both
> >inf-ptrace.c and infptrace.c. It eliminates the calls to call_ptrace
> >and ptrace_wait.
> >
> >Andrew has recently suggested that we'd want debugging support for the
> >ptrace(2) interface, which could be implemented by using call_ptrace()
> >unconditionally.
>
> Having, again, spent some time debugging GNU/Linux threads, I'm pretty
> much certain of this.
I completely agree.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-09-20 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 19:14 Mark Kettenis
2004-09-20 19:37 ` Andrew Cagney
2004-09-20 19:42 ` Daniel Jacobowitz [this message]
2004-09-20 21:48 ` Mark Kettenis
2004-09-21 13:09 ` Andrew Cagney
2004-09-24 22:37 ` Mark Kettenis
2004-09-24 22:46 ` Andrew Cagney
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=20040920194212.GA10736@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
/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