parser-test.exe fails on Win32 MinGW

Hi,

I tried the new RTT 1.10.1 release on Win32 with MinGW. For the first time the build process of the RTT shared library and all tests was straight forward without any problems and errors - really great :O).

On execution of the test cases all tests passed except of the parser-test.exe. This test failed with segmentation fault. I started the debugger to find the reason for the crash. The test crashes on line 275 of dispatch_test.cpp.

I can set a breakpoit on line 275 and the execution stops on this breakpoint. If I try to step into the function parser.parseProgramm( prog, tc) the debugger stops with "signal-received" and the following stack trace (see attachment).

Any idea what is going wrong here before I dig deeper?

Regards, Uwe

AttachmentSize
parser_test_stack_trace.txt324.62 KB

parser-test.exe fails on Win32 MinGW

Hi Uwe,

On Sat, Oct 24, 2009 at 17:20, <uwe_kindler [..] ...> wrote:
> Hi,
>
> I tried the new RTT 1.10.1 release on Win32 with MinGW. For the first time
> the build process of the RTT shared library and all tests was straight
> forward without any problems and errors - really great :O).
> On execution of the test cases all tests passed except of the
> parser-test.exe. This test failed with segmentation fault. I started the
> debugger to find the reason for the crash. The test crashes on line 275 of
> dispatch_test.cpp.
>
> I can set a breakpoit on line 275 and the execution stops on this
> breakpoint. If I try to step into the function parser.parseProgramm( prog,
> tc) the debugger stops with "signal-received" and the following stack trace
> (see attachment).
>
> Any idea what is going wrong here before I dig deeper?

Thanks for the backtrace, but could you open a bug report to store
such attachments ? It will make it easier for us to track this issue
and they are rather large for the mailing list.

I don't know yet what causes this, because the crash happens in a
function the parser shouldn't be (there is no named constant in the
snippet being parsed). So this might be caused by an earlier
corruption. We'll need a memory checker or something to figure this
out. Also, you should compile the RTT with CMAKE_BUILD_TYPE=Debug such
that we get more debug info in the backtrace.

Peter