qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] fix interaction with noexecstack
Date: Sat, 04 Sep 2004 16:45:08 +0200	[thread overview]
Message-ID: <pan.2004.09.04.14.45.07.440321@reply.to> (raw)
In-Reply-To: 4139B2C3.6000203@volny.cz

Le Sat, 04 Sep 2004 14:19:15 +0200, Filip Navara a écrit :

> Fabrice Bellard wrote:
> 
>> The patch seems OK for me, at least until the instruction cache is
>> dynamically allocated.
> 
> I haven't tried the patch, but there isn't any "mprotect" function on
> Windows so I guess it would break MinGW builds. See the code below. It
> should work, but *I HAVEN'T TESTED IT*:
> 

Tested, need to include <winbase.h> (and <windows.h>).
gcc juste produce a warning with VirtualProtect:
/home/ronald/Prog/Win32/combo/qemu/exec.c: Dans la fonction « page_init »:
/home/ronald/Prog/Win32/combo/qemu/exec.c:155: AVERTISSEMENT: passage de
arg 1 de « VirtualProtect » transforme en pointeur un entier sans
transtypage

aproximative translation: in function page_init passing arg1 of
VirtualProtect is making pointer from integer without a cast.

Note: with **VirtualProtect or *VirtualProtect make is aborting, I have
used VirtualProtect.

  reply	other threads:[~2004-09-04 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-04  0:00 [Qemu-devel] [PATCH] fix interaction with noexecstack Lennert Buytenhek
2004-09-04  0:15 ` Lennert Buytenhek
2004-09-04 10:49 ` Fabrice Bellard
2004-09-04 12:19   ` Filip Navara
2004-09-04 14:45     ` Ronald [this message]
2004-09-04 16:15       ` [Qemu-devel] " Filip Navara
2004-09-04 17:07         ` [Qemu-devel] " Ronald
2004-09-07  7:59           ` Hartmut Birr
2004-09-05 14:13         ` [Qemu-devel] " Lennert Buytenhek
2004-09-29 21:23         ` Fabrice Bellard

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=pan.2004.09.04.14.45.07.440321@reply.to \
    --to=look@reply.to \
    --cc=daimon55@free.fr \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).