#611 Crash or hang with SYSINI

v4.0beta
closed
5
2012-08-14
2009-04-15
Mark Harsen
No

I have a rather large OOREXX application that won't start under beta 4.0 4382 and I traced the hang to a call sysini statement. The following test program also hangs on the CALL SYSINI directive:

Trace I
App="THOR STARTUP"
Ini="D:\Work\Clear-shared--2.ini"
Call SysIni Ini, App, "ALL:", "Keys."
Say Keys.0
Do I = 1 to Keys.0
Say I Keys.I
End

D:\Work\Clear-shared--2.ini is a decrypted version of a shared authentication file for network equipment and contains lots of information that can't be shared, sorry. I've not tried this on a dummy file yet, but does this give you enough to work on or do you need me to do more testing or provide more information?

Thank you, -Mark

Discussion

  • Mark Miesfeld

    Mark Miesfeld - 2009-04-15

    Thanks for reporting this Mark. I'll take a look at it a little later.

    You might want to try writing a small INI file with only a few items in it and trying that with a simple program. If you do and it reproduces the hang, please attach the INI file and simple program to this bug. It will save me having to write them myself.

     
  • Mark Harsen

    Mark Harsen - 2009-04-15

    Here's a two-line, dummy .ini file which also hangs using the above program:

    [THOR STARTUP]
    load dummy=my.password

    Thank you, -Mark

     
  • Rick McGuire

    Rick McGuire - 2009-04-15

    Mark, I'm able to recreate this, but only with the NODEBUG build. The top of the stack looks like it's in rexxutil, but I'm not sure I know how to figure out where.

     
  • Mark Miesfeld

    Mark Miesfeld - 2009-04-15

    SysIni example from reference doc

     
  • Mark Miesfeld

    Mark Miesfeld - 2009-04-15

    Rick,

    There is an example from the reference doc. I've attached it. It crashes the interpreter, again the no-debug build. I was just going to switch to a debug build, haven't tried yet.

    The call stack shows the crash is in rexxutil:

    rexxutil.dll!000000006b123757()
    [Frames below may be incorrect and/or missing, no symbols loaded for rexxutil.dll]
    rexx.dll!000000000030f558()
    rexx.dll!000000000031039f()
    rexx.dll!00000000002cd391()
    rexx.dll!000000000030affa()
    rexx.dll!0000000000353fe9()
    rexx.dll!00000000002f29c7()
    rexx.dll!0000000000344612()
    rexx.dll!00000000002f78e4()
    rexx.dll!0000000000309561()
    rexx.dll!00000000002cd7ef()
    rexx.dll!00000000003030d1()
    rexx.dll!000000000030bb0b()
    rexx.dll!00000000002fe01d()
    rexx.dll!0000000000305053()
    rexx.dll!0000000000318403()
    rexx.exe!00000001400016c9()
    rexx.exe!0000000140001ea5()
    kernel32.dll!0000000077d596ac()

     
  • Rick McGuire

    Rick McGuire - 2009-04-15

    The debug build appears to be working just fine for me, only the debug build seems to have a problem. I don't know how to translate those addresses into the code locations.

     
  • Mark Miesfeld

    Mark Miesfeld - 2009-04-15

    I should have mentioned I'm on 64-bit.

    I did get a crash with my debug build, but something was munged. Symbols were only loaded for rexxutil.dll, not for rexx.dll.

    Let me play with it a bit and I'll see if I can either get a good debug session, or good addresses

     
  • Rick McGuire

    Rick McGuire - 2009-04-15

    I found the problem. there was a missed update with the const char * cleanup.

     
  • Rick McGuire

    Rick McGuire - 2009-04-15

    Committed revision 4392.

     
  • Mark Harsen

    Mark Harsen - 2009-04-21

    Thank you guys, all testing indicates that this works perfectly now. I REALLY appreciate the fantastic work you are doing! Sincerely, -Mark

     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks