From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: sathish kumar <sathishs_45@yahoo.com>,
rajesh-siso <rajesh.uvce@gmail.com>
Subject: Re: [Qemu-devel] Regarding PTRACE implementation in QEMU user mode
Date: Tue, 23 Sep 2008 15:20:51 +0100 [thread overview]
Message-ID: <200809231520.51803.paul@codesourcery.com> (raw)
In-Reply-To: <200809231512.40813.paul@codesourcery.com>
On Tuesday 23 September 2008, Paul Brook wrote:
> > Can someone explain why explain why ptrace system call is not implemented
> > in QEMU? if someone is working on it, please share some ideas.
>
> Because it's extremely hard (read: nearly impossible) to implement
> properly.
I'll also note that the usual use of ptrace if for gdb/gdbserver. You should
use the builtin qemu gdb stub instead.
Paul
next prev parent reply other threads:[~2008-09-23 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 14:01 [Qemu-devel] Regarding PTRACE implementation in QEMU user mode sathish kumar
2008-09-23 14:12 ` Paul Brook
2008-09-23 14:20 ` Paul Brook [this message]
2008-09-23 15:02 ` Jamie Lokier
2008-09-23 18:29 ` Kirill A. Shutemov
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=200809231520.51803.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=rajesh.uvce@gmail.com \
--cc=sathishs_45@yahoo.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;
as well as URLs for NNTP newsgroup(s).