From: Jeff Dike <jdike@addtoit.com>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: BlaisorBlade <blaisorblade_spam@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Bad handling of invalif systemcalls
Date: Fri, 22 Oct 2004 17:02:15 -0400 [thread overview]
Message-ID: <200410222102.i9ML2FWY005227@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Fri, 22 Oct 2004 10:12:43 +0200." <4178C0FB.4070108@fujitsu-siemens.com>
bstroesser@fujitsu-siemens.com said:
> Maybe it would make sense, to change the debugger-code. It could
> accept (SIGTRAP|0x80) and give it to the real debugger as SIGTRAP
> normally. Also, it could accept a ptrace(PTRACE_SETOTIONS,,,PTRACE_O_TR
> ACESYSGOOD) and after this it could relay the (SIGTRAP|0x80) without
> change.
Yeah, it would, but what you have now will work for the time being.
> You are right, orig_eax on the processes stack is -1. But this *has*
> to be saved in the tt-regs structure for later use. What I'm doing is
> the same that
> UPT_SYSCALL_NR(TASK_REGS(task)) = PT_SYSCALL_NR(proc_regs); does
> in the case of a systemcall. I used "-1" instead of
> "PT_SYSCALL_NR(proc_regs)" because it *is* the same in this situation.
Right, good point.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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-10-22 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 15:25 [uml-devel] Bad handling of invalif systemcalls Bodo Stroesser
2004-10-21 17:32 ` BlaisorBlade
2004-10-22 7:33 ` Bodo Stroesser
2004-10-21 22:09 ` [uml-devel] " Jeff Dike
2004-10-21 22:32 ` BlaisorBlade
2004-10-22 4:14 ` Jeff Dike
2004-10-22 8:14 ` Bodo Stroesser
2004-10-22 8:12 ` Bodo Stroesser
2004-10-22 21:02 ` Jeff Dike [this message]
2004-10-25 14:49 ` Bodo Stroesser
2004-10-25 15:21 ` Bodo Stroesser
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=200410222102.i9ML2FWY005227@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.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