Menu
▾
▴
[Oorexx-bugs] [ oorexx-Bugs-3501117 ] Crash at end of program
|
From: SourceForge.net <no...@so...> - 2012-03-10 15:52:25
|
Bugs item #3501117, was opened at 2012-03-10 02:12 Message generated for change (Comment added) made by jfaucher You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3501117&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rony G. Flatscher (orexx) Assigned to: Nobody/Anonymous (nobody) Summary: Crash at end of program Initial Comment: This is with ooRexx 4.1.1 beta (build date: Feb 26 2012), Windows XP SP 3. Received a short Rexx test program, which uses the ooRexx framework log4ooRexx. Upon termination (the last logged entry in the logfile can be found after the crash in the file) a Windows crash popup window occurs. To duplicate: please download the attached file and unzip it. Then run "rexx-log-test.rex". At the end of the run the exception occurs. ---------------------------------------------------------------------- >Comment By: jfaucher (jfaucher) Date: 2012-03-10 07:52 Message: I had the crash with the first attached file. What I see under debugger is that : uninit is sent to the targetStream of FileAppender (by lastChanceUninit) --> the variable "CSELF" is dropped and then uninit is sent to the FileAppender --> log4rexx_appender.cls:621 targetStream~charout(self~layout~footer) : crash because stream_info is NULL (no "CSELF" variable in the context) More details in the attached file jlf_debug.txt A possible fix could be to test if stream_info is NULL (already done in stream_close and stream_uninit). If this is the right way to fix the crash, then we should review all the functions which depend on CSELF and make them support the case NULL. I can do that, just tell me... ---------------------------------------------------------------------- Comment By: Rony G. Flatscher (orexx) Date: 2012-03-10 06:32 Message: Now I can reproduce the crash on XP SP3 with ooRexx 4.1.1 in any command line window; this version makes sure that required/called programs/packages are in a different directory than the Rexx program (log-test.rex) that gets executed. Steps to setup the crashing version: - unzip "crash_log4rexx_20120310-with-needed-setup.zip" - open command line window, change into "work\crash" directory and run: - setEnvironment.bat (will prepend PATH with superdirectory "..") - rexx log-test.rex [In case it is important, information on log4oorexx <http://wi.wu-wien.ac.at/rgf/rexx/orx18/log4r/2007_orx18_log4rexx-20070517-article.pdf>, via: <http://wi.wu-wien.ac.at:8002/rgf/rexx/orx18/log4r/> ---------------------------------------------------------------------- Comment By: Rony G. Flatscher (orexx) Date: 2012-03-10 06:03 Message: By accident I ended up with a new command line window and re-ran the test program without a problem. Switching to the previous window and running the same program there still causes the crash in Rexx. Although the PATH is different (added two directories) I am not able to identify a possible cause for this. There is no other Rexx or reltated file, the Rexx program itself uses "pure ooRexx". So, if there is anything I can research, please advise, I try to keep the command-line windows open and not reboot the PC today. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3501117&group_id=119701 |