From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Sam T Sander <ssander@rocketmail.com>
Subject: Re: [uml-devel] fixing ptrace for ARM
Date: Sun, 29 Aug 2004 23:41:10 +0200 [thread overview]
Message-ID: <200408292341.10362.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040827171904.42460.qmail@web12504.mail.yahoo.com>
Alle 19:19, venerdì 27 agosto 2004, Sam T Sander ha scritto:
> As a first step toward porting UML to ARM, I need to fix ptrace to modify
> system call numbers. Unfortunately, I don't know where to start. Can
> anyone point me in the right direction? Has anyone looked into this for ARM
> or any of the other ports? What was changed in the X86 ptrace to fix it?
I think that the work must be done in the stack layout on ptracing (read the
handle_trap() function for what UML does). But also see this URL:
http://perso.wanadoo.fr/laurent.vivier/UML/
One of the nice thing of those patches is that if you implement something
similar (which is a lot easier IMHO) you don't need to be able to change
system call numbers.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id\x10808&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-08-29 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 17:19 [uml-devel] fixing ptrace for ARM Sam T Sander
2004-08-29 21:41 ` BlaisorBlade [this message]
2004-08-30 13:14 ` Sam T Sander
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=200408292341.10362.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=ssander@rocketmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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