Le 17/10/2011 14:17, Adrien a écrit :

On 15/10/2011, Emmanuel Dieul <emmanuel.dieul@free.fr> 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

Although the message told me I've a core dumped, I have no core: I only have a stack trace.
It's the first time I use gdb. However, I found how to run my program into gdb. It produced the
same kind of error. Here, I could have more information :

(gdb) r
...
[New Thread 6724.0x1590]
[New Thread 6724.0x131c]
[New Thread 6724.0x1ad8]
[New Thread 6724.0xf6c]
[New Thread 6724.0x1920]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 6724.0x14ac]
0x610e73da in pthread::thread_init_wrapper(void*) () from /cygdrive/l/programmation/cygwin/bin/cygwin1.dll
(gdb) backtrace
#0 0x610e73da in pthread::thread_init_wrapper(void*) () from /cygdrive/l/programmation/cygwin/bin/cygwin1.dll
#1 0x762b2ad6 in OutputDebugStringA () from /cygdrive/c/Windows/syswow64/KERNELBASE.dll
#2 0x40010006 in ?? ()
#3 0x00000000 in ?? ()
(gdb)

So, it seems cygwin is in trouble with my program... Damn !