From mint-bounce@lists.fishpool.fi Sat Dec 19 07:22:14 2009 Message-ID: <1737922A38A54A92A034771EA96AC479@mercatus.local> From: "Jo Even Skarstein" To: References: <4B2CB191.8000608@freesbee.fr> <4B2CB564.1050807@freesbee.fr> In-Reply-To: <4B2CB564.1050807@freesbee.fr> Subject: Re: [MiNT] XaAES trap sanitizer Date: Sat, 19 Dec 2009 13:19:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-EsetScannerBuild: 6227 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: ------------------------------------------------- From: "Vincent Rivière" Sent: Saturday, December 19, 2009 12:13 PM To: Subject: Re: [MiNT] XaAES trap sanitizer >> Here is a patch for sanitizing the usage of traps in XaAES. > > And since XaAES uses GemLib I really wonder why it has to mess with traps. I'm not sure if I understand what you mean here. XaAES obviously has to use traps when calling the VDI. The VDI bindings are (IIRC) in GemLib. Jo Even __________ Information from ESET NOD32 Antivirus, version of virus signature database 4694 (20091216) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com