From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id KAA04802 for caml-redistribution; Thu, 4 Mar 1999 10:11:15 +0100 (MET)
Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id WAA08334 for <caml-list@pauillac.inria.fr>; Wed, 3 Mar 1999 22:50:20 +0100 (MET)
Received: from mail3.microsoft.com (mail3.microsoft.com [131.107.3.123])
	by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id WAA03526
	for <caml-list@inria.fr>; Wed, 3 Mar 1999 22:50:18 +0100 (MET)
Received: by mail3.microsoft.com with Internet Mail Service (5.5.2524.0)
	id <GHDG9HNB>; Wed, 3 Mar 1999 13:50:16 -0800
Message-ID: <25983782061AD111B0800000F86310FE1026CB4B@RED-MSG-42>
From: Manuel Fahndrich <maf@microsoft.com>
To: "'caml-list@inria.fr'" <caml-list@inria.fr>
Subject: Debugger under Windows...
Date: Wed, 3 Mar 1999 13:50:07 -0800 
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: weis

[Version francaise]

Quel sont les probleme pour adapter le debugger OCAML pour Windows? Est-t-il
juste une question d'adapter l'interface graphique du debugger meme, oubien,
est-ce qu'il y a des problemes au niveau de la generation de code x86 pour
debuggage?





[English version]
What would be involved in porting the OCAML debugger to Windows?

- Is the problem just the debugger application and the graphical user
interface, or

- the generation of debuggable OCAML code by the compiler under windows.

I'm especially interested in the native code debugger, but even a bytecode
debugger would be useful under Windows.


Manuel Fahndrich	Microsoft Research

"Expressed opinions are my own and do not necessarily reflect those of my
employer."