On 27 févr. 07, at 08:22, Ilya Shar wrote:
Please see the diff file attached.
I meant send a diff to the qemu-devel in a new mail with [Patch] in
the subject so that it can be committed :-)
However, at second thought, I think that it might need some re-work,
see [1], and the arguments m
--- Pierre d'Herbemont <[EMAIL PROTECTED]> wrote:
> ...
> cvs diff -u would be easier to read for me. (or diff
> -u). You could
> send this patch to the qemu-devel, that would be
> cool.
>
Pierre,
Please see the diff file attached.
> ...
> Ouch! I have noticed the same: qemu can trigger bu
On 23 févr. 07, at 23:56, Ilya Shar wrote:
Sure. At first I was hitting unsupported mach
syscalls, so I modified darwin-user/syscall.h
according to
/Developer/SDKs/MacOSX10.3.9.sdk/usr/include/mach/syscall_sw.h
:
$ diff syscall.c syscall.c.orig
458,465d457
< case -33:
< DPRINTF("s
--- Pierre d'Herbemont <[EMAIL PROTECTED]> wrote:
Hi Pierre,
Thanks for your reply - please see comments inserted
below:
> Hi Ilya!
>
> On 23 févr. 07, at 21:32, Ilya Shar wrote:
>
> > I'm running i386-darwin-usrer on i386 and some
> apps
> > (Safari browser) crash because cmpxchg8b attempts
Hi Ilya!
On 23 févr. 07, at 21:32, Ilya Shar wrote:
I'm running i386-darwin-usrer on i386 and some apps
(Safari browser) crash because cmpxchg8b attempts to
wrie to a qemu-allocated page which is readable but
write-protected. When I comment out mprotect in
exec.c
Are you sure it does Safari
Hi,
I'm running i386-darwin-usrer on i386 and some apps
(Safari browser) crash because cmpxchg8b attempts to
wrie to a qemu-allocated page which is readable but
write-protected. When I comment out mprotect in
exec.c
//mprotect(g2h(page_addr),
qemu_host_page_size,
// (pr
