Moritz, Are you doing a build in between these different sizes? There was a problem on Windows with the build order where sometimes some things got left out.
-- Mark Miesfeld On Mon, Jul 14, 2008 at 1:11 AM, Moritz Hoffmann <[EMAIL PROTECTED]> wrote: > Hi, > oorexx 4 works for me as well, I can compile and run it by now - on my > Dedian machine. Thanks for the effort. > > However, rexx sometimes fails to load the rexx image. Here is a stack trace. > > #0 RexxMemory::restoreImage (this=0xb7f20120) > at ./kernel/runtime/RexxBehaviour.hpp:100 > #1 0xb7ece583 in RexxMemory::initialize (this=0xb7f20120, > _restoringImage=true) at ./kernel/runtime/RexxMemory.cpp:197 > #2 0xb7ead4db in Interpreter::startInterpreter (mode=RUN_MODE) > at ./kernel/runtime/Interpreter.cpp:135 > #3 0xb7ead234 in Interpreter::createInterpreterInstance > (options=0xbfa27bac) > at ./kernel/runtime/Interpreter.cpp:252 > #4 0xb7ead2e7 in InstanceBlock (this=0xbfa27c14, exits=0x0, > env=0x8048b88 "bash") at ./kernel/runtime/Interpreter.cpp:381 > #5 0xb7ea7a33 in ActivityDispatcher::invoke (this=0xbfa27c58, exits=0x0, > env=0x8048b88 "bash") at ./kernel/runtime/ActivityDispatcher.cpp:118 > #6 0xb7e6e309 in RexxStart (argcount=0, arglist=0xbfa29d1c, > programname=0xbfa2bcce "../../test/trunk/testOORexx.rex", instore=0x0, > envname=0x8048b88 "bash", calltype=0, exits=0x0, retcode=0xbfa29d26, > result=0x0) at ./kernel/api/InterpreterAPI.cpp:172 > #7 0x08048ab0 in main (argc=2, argv=0xbfa29dd4) > at ./platform/unix/rexx.cpp:168 > (gdb) bt full 1 > #0 RexxMemory::restoreImage (this=0xb7f48120) > at ./kernel/runtime/RexxBehaviour.hpp:100 > imagesize = 730984 > objectPointer = 0xb7756118 "\f\017\211÷LPu·" > endPointer = 0xb7807770 "" > imageBehav = <value optimized out> > primitiveBehaviours = <value optimized out> > primitiveTypeNum = <value optimized out> > i = <value optimized out> > > It seems like the rexx.img size is sometimes wrong, the file has 600660 > bytes here, when debugging it usually has the currect number here... > Moritz > > > > David Ashley wrote: >> All - >> >> I finally got around to testing 4.0 on Linux. Running rexx -v works but >> nothing else does. Everything I try, including rexxtry.rex, gives a >> segmentation fault. I have not tried to debug this yet but I wanted to >> give everyone a heads up. >> >> Thanks, >> W. David Ashley > > > -- > Moritz Hoffmann > http://antiguru.de/ > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
