On 15/10/2011, Emmanuel Dieul <[email protected]> wrote: > Hi all, > > I'm developing a little game using ocaml and lablgtk2. During the game > (under cygwin), I've got a segmentation fault for ocamlrun : >> >> >> [emmanuel@localhost ~/]$ cat ocamlrun.exe.stackdump >> Exception: STATUS_ACCESS_VIOLATION at eip=610E73DA >> eax=1BDCCE64 ebx=01E1C530 ecx=75A50C48 edx=00000000 esi=01E1C588 >> edi=1BB8CE64 >> ebp=1BB8CD98 esp=1BB8CD60 >> program=L:\programmation\cygwin\bin\ocamlrun.exe, pid 6260, thread unknown >> (0x1CBC) >> cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B >> Stack trace: >> Frame Function Args >> 1BB8CD98 610E73DA (01E1C530, 1BB8CDD4, 610E73A0, 01E1C530) >> End of stack trace >> [emmanuel@localhost ~/]$ ocaml -version >> The Objective Caml toplevel, version 3.12.0 > > > Is there a way to know if the problem comes from ocamlrun or if it comes > from the (labl)gtk libraries for windows?
Hi, Do you have a backtrace? You could run your application under gdb and use its "backtrace" function to get one. It should show quite quickly whether the issue is from lablgtk, gtk or something else. Regards, Adrien Nader -- Caml-list mailing list. Subscription management and archives: https://sympa-roc.inria.fr/wws/info/caml-list Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
