From: Brandon C. <br...@sa...> - 2010-02-22 20:52:54
|
> This appears like the symptoms of a garbage collection problem that > occurred at some other location. A couple of things you might want to > try displaying. > > First of all, what is the value of variable len2? 4294967295 > Secondly, what are the values of other and otherObj? I'm most > interested at this point in whether they are the same. other: 0x7fd61aa8 {stringrep=0x7fd63148 value=-1 } otherObj: 0x7f2549d0 {objectVariables=0x7f254b28 operatorMethods=0x003cd908 classInstance=0x7fcbf578 } not the same > Expand the display of the variable other to display the entire object. > Expand all of the "+" in the tree and give me that entire display. [RexxInteger] = {stringrep=0x7fd63148 value=-1 } RexxObject = {objectVariables=0x00000000 operatorMethods=0x003cd908 classInstance=0x7fcbf578 } operatorMethods = 0x003d0dc0 class RexxObject * (thiscall RexxObject::** RexxString::operatorMethods)(void) classInstance = 0x7fce3918 {id=0x7fce3960 classMethodDictionary=0x7fce3990 instanceBehaviour=0x003d39b8 ...} hashValue = 2144743752 length = 4294967295 NumberString = 0x00000000 {number=0x00000028 <Bad Ptr> } Attributes = 3831652 stringData = 0x7fd61acc " " > > Also, if you go back down the stack to the > RexxInstructionMessage::execute call, and expand the "this" variable > until you find the instructionLocation variable. I'm interested in > the start line field. > > Now go down one more frame to the RexxActivaiton::run() call. Again, > expand the "this" variable. You are looking for the value > "this->sourceObject->programName->stringData", which should be the > name of the program that is currently running. Combine that with the > startLine information from above. this will give you the line being > executed at the time of the crash. I'd like to see the Rexx source > line for this. 321 if \ch~completed() then do 322 sock~close() >323 self~log('Socket' sock 'For Client' peer~address() 'Killed Due To Timeout!', 'd') 324 end > > Rick -- Brandon Cherry Network Engineer, Safe Data, Inc. (910) 285-7200 ext 3017 http://www.safedatausa.com/ On 2/22/2010 10:41 AM, Brandon Cherry wrote: > Unfortunately, I do not have the debugger still running on this one. > This error occurred over the weekend. It ran for 4 days straight (the > longest so far). > > I will try to keep the debugger running so we can track this down next time. |