segmentation fault in latest testape release in cygwin

[Martin (obo. Joakim)]

Hi,

I’ve taken over some old unit tests, which uses testape. Unfortunately I’ve had problems running them, since they segfaultwhen run. Turns out anything built with the latest testape release 1171 will segfault for me, while anything built with testaper880 will work just fine. I would prefer to run the latest release. Do you have any idea what might be causing the segfault?


I’m using 32bit Cygwin on a win7 64bit machine. Example gdb output (from one of the included samples):

$ gdb sample1.exe
GNU gdb (GDB) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from sample1.exe...done.
(gdb) run
Starting program: /cygdrive/c/Users/jlinde2/Downloads/testape-1171/samples/sample1.exe
[New Thread 4308.0x11c8]
[New Thread 4308.0x1cb4]

Program received signal SIGSEGV, Segmentation fault.
0x00405cc5 intestape_node_last ()
(gdb) bt
#0 0x00405cc5 in testape_node_last ()
#1 0x00404768 in testape_exception_handler ()
#2 0x004048d4in testape_exception_handler ()
#3 0x0040377c in testape_error ()
#4 0x00407af2 in testape_validate_call ()
#5 0x00406903 in testape_stub_value ()
#6 0x00406b5a in testape_mocking_handle_pre ()
#7 0x00404dc8 in testape_stub_executed ()
#8 0x0040126a in __ms_vsnprintf ()
#9 0x00403332 in main ()



[Martin Nielsen]

Hi Joakim

Thank you for reporting this error.

Cygwin/gcc has not been part of the platforms that is being tested before a release – the assumption being ( and the has been true for several releases) that mingw would work just fine with cygwin/gcc also. Apparently this is not the case anymore, with the version of mingw-w64 that I used to build the windows releases.

The problem is easy for me to reproduce – e.g. when I run sample1, I noticed that defaults mocks are created for a couple of windows library functions – one of them being __ms_vsnprintf. I think that this means that gcc is not linking with the build-in library on windows, but instead with the cygwin equivalents.

There used to be a option to cygwin/gcc to use windows libraries (the -mno-cygwin option), but this is no longer to be found in the GCC that I installed for cygwin yesterday, but if you have it in your gcc, you could try that.

Alternatively you can use mingw-w64 for the tests, but I realize that this is a big step.

Anyway, I will work on a solution, and let you know, once I have it figured out.

[Martin Nielsen]

Hi Joakim

The testape library supplied in release 1171 for windows are compiled with a gcc having the following signature

Target: i686-w64-mingw32
Configured with: --host=i686-w64-mingw32 --build=i686-w64-mingw32 --target=i686-w64-mingw32


So you need a compatible gcc compiler installed in cygwin. I have used the packages mingw64-i686-binutils and mingw64-i686-gcc in a fresh cygwin installation and they produce object files that are compatible with testape.a

Unfortunately there is one more twist: TestApe do not recognize i686-w64-mingw32-gcc.exe, so you also need to add a symbolic link for gcc and point it to i686-w64-mingw32-gcc.exe, e.g

$ ln /usr/bin/i686-w64-mingw32-gcc.exe /usr/bin/gcc.exe


Finally you you need to provide the -mgw option when you compile to trigger the usage of the build in windows standard library msvcrt.lib.

With that in mind, sample26 can be compiled like this

$ testape -mgw gcc sample26.c converter.c testape.a


Next beta wil contain a fix for the problem about not being able to recognize i686-w64-mingw32-gcc.exe

Br,
Martin