2013/11/5 Ruben Van Boxem <vanboxem.ru...@gmail.com>
>
>
> If you have pthreadGC2.dll, you are not using winpthreads, but
> pthreads-win32, an older and completely different project. What toolchain
> are you using? I don't think you're using MinGW-w64, but the older and less
> complete MinGW(.org).
>
> You can get MinGW-w64 from here:
> http://sourceforge.net/projects/mingwbuilds/files/mingw-builds-install/mingw-builds-install.exe
>
> Or seperate downloads via here:
> http://mingw-w64.sourceforge.net/download.php#mingw-builds
>
>
Initially I was using MinGW(.org), supposing the problem would be
inherited. So now I have tested on MinGW-w64. The crash happens just the
same (see below), except that gdb figures it out at libwinpthread-1.dll.
I'll try to look into the problem a little bit more tomorrow. Maybe test
with named semaphores and see how the cookie crumbles.
------------------------------------
gcc --version
gcc.exe (rev5, Built by MinGW-W64 project) 4.8.1
This GDB was configured as "x86_64-w64-mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from d:\GIT\tubo\src\.libs\example.exe...done.
(gdb) run
Starting program: d:\GIT\tubo\src\.libs\example.exe
[New Thread 5920.0x404]
command (exit to end):ls
found: D:\msys\1.0\bin\ls.exe
exec> Main process id = 0x1720
0x1720: Tubo_exec thread processing: Makefile
0x1720: Tubo_exec thread processing: Makefile.am
0x1720: Tubo_exec thread processing: Makefile.in
0x1720: Tubo_exec thread processing: example-example.o
0x1720: Tubo_exec thread processing: example-tubo.o
0x1720: Tubo_exec thread processing: example-tubo_exec.o
0x1720: Tubo_exec thread processing: example.c
0x1720: Tubo_exec thread processing: example.exe
0x1720: Tubo_exec thread processing: libtubo.dll
0x1720: Tubo_exec thread processing: libtubo.la
0x1720: Tubo_exec thread processing: libtubo_la-tubo.lo
0x1720: Tubo_exec thread processing: libtubo_la-tubo.o
0x1720: Tubo_exec thread processing: libtubo_la-tubo_exec.lo
0x1720: Tubo_exec thread processing: libtubo_la-tubo_exec.o
0x1720: Tubo_exec thread processing: tubo.c
0x1720: Tubo_exec thread processing: tubo.h
0x1720: Tubo_exec thread processing: tubo_exec.c
0x1720: Tubo_exec thread processing: tubo_exec.c~
0x1720: Tubo_exec thread processing: tubo_exec.i
0x1720: Tubo_exec thread processing: tubo_exec.i~
0x1720: Tubo_exec thread processing: tubo_main.c
0x1720: Tubo_exec thread processing: tubo_static.i
0x1720: Tubo_exec thread processing: tuboexec-tubo.o
0x1720: Tubo_exec thread processing: tuboexec-tubo_main.o
0x1720: Tubo_exec thread processing: tuboexec.exe
0x1720: Tubo_exec thread processing:
command (exit to end):[New Thread 5920.0x1ad0]
[New Thread 5920.0x16bc]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 6932.0x1ba0]
0x000000006494313a in ?? () from d:\mingw64\bin\libwinpthread-1.dll
-------------------
>
>
--
------------------------------------------------------------------------------------
Dr. Edscott Wilson Garcia
Applied Mathematics and Computing
Mexican Petroleum Institute
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
