[Oorexx-bugs] [ oorexx-Bugs-2703908 ] rxapi crash at revision 4300

[SourceForge.net <no...@so...>]

Bugs item #2703908, was opened at 2009-03-22 14:55
Message generated for change (Settings changed) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2703908&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interpreter
Group: v4.0beta
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Mark Miesfeld (miesfeld)
>Assigned to: Rick McGuire (bigrixx)
Summary: rxapi crash at revision 4300

Initial Comment:
Rick,

There is a repeatable crash in rxapi at revision 4300.  It's probably always been there, I just threw in the 4300 so the bug title would be unique.

I'm stumped with it, so it will probably need your touch.  I've attached a zip file with the stuff to recreate it.

What makes it hard, for me, is that it only happens with a release build.  I can run the program that causes the crash under a debug build a thousand times and it never crashes.

The zip file has source and a simple make file, also the compiled executable.

The executable uses RexxStart() in a loop to run the  included simple Rexx program 5 times.  Run the program from the command line several times in a row.  On the third execution from the command line, at the first invocaton of RexxStart(), it always crashes in rxapi.

I threw in a copy of the stack at the time of the crash, I always have the exact same stack. I can trace the sequence using the rxapi map file. It always goes:

processMessages -> dispatch -> createSessionQueue -> 

queue = new DataQueue(session);

then a malloc in rxapi and a crash down in the kernel.

But, from there I'm stuck.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2009-03-22 15:58

Message:
Rick, the program doesn't crash on 64-bit Windows.  I should have tried
that before.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2703908&group_id=119701