Le 17/10/2011 22:40, ygrek a écrit :

On Mon, 17 Oct 2011 18:32:53 +0200
Emmanuel Dieul <emmanuel.dieul@free.fr> wrote:

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 !

OutputDebugStringA means there should be some useful info.
Run it under windbg to see the message.
Also look into system event logs.

I tried to look after system logs, but I found nothing about this event.
I looked into Application and System logs of Windows, but I found nothing.

I also tried to run my program under windbg. With my first run (command GN
twice), I could see my program running and then stop with the same kind of error
(STATUS_ACCESS_VIOLATION).
However, I don't understand anything of what windbg told me :

0:000> KP 20
Child-SP RetAddr Call Site
00000000`0008e318 00000000`74b8601a ntdll!NtTerminateProcess+0xa
00000000`0008e320 00000000`74b7cf87 wow64!Wow64EmulateAtlThunk+0x86ba
00000000`0008e350 00000000`74b02776 wow64!Wow64SystemServiceEx+0xd7
00000000`0008ec10 00000000`74b7d07e wow64cpu!TurboDispatchJumpAddressEnd+0x2d
00000000`0008ecd0 00000000`74b7c549 wow64!Wow64SystemServiceEx+0x1ce
00000000`0008ed20 00000000`77384956 wow64!Wow64LdrpInitialize+0x429
00000000`0008f270 00000000`77381a17 ntdll!RtlUniform+0x6e6
00000000`0008f760 00000000`7736c32e ntdll!RtlCreateTagHeap+0xa7
00000000`0008f7d0 00000000`00000000 ntdll!LdrInitializeThunk+0xe
0:000>

As I'm clearly not even a usual user, this is completely unknown for me.