Thanks for all of the help! Glad I could help you track it down.
It is kind of interesting to delve into how the interpreter works as
well. Some of this sounds familiar to the talk at the last symposium in
Raleigh.
--
Brandon Cherry
Network Engineer, Safe Data, Inc.
(910) 285-7200 ext 3017
http
Brandon,
I figured out the problem from the information you provided. Thanks
for the excellent job at extracting the information I asked for. That
gave me enough clues to figure this out. I've opened a tracker item
for this because I was able to reproduce the problem in about 4 lines.
https://
I doubt that's the problem. My suspicion is the string value from the
socket is getting prematurely garbage collectednow I just need to
figure out why. I suspect you can make this go away by changing that
line to
>323self~log('Socket' sock~string 'For Client' peer~address() 'Killed
D
After looking at lines 322 and 323, I think they should be reversed.
What happens if the socket goes away and then you try to log out stuff
from the socket?
--
Brandon Cherry
Network Engineer, Safe Data, Inc.
(910) 285-7200 ext 3017
http://www.safedatausa.com/
On 2/22/2010 3:52 PM, Brandon Cher
> 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
> inte
This time the debugger is still up.
Running from trunk rev 5561.
Error:
Unhandled exception at 0x0036c80c (rexx.dll) in rexx.exe: 0xC005:
Access violation reading location 0x7fd7.
Threads:
0 3060Main Thread Main Thread SysSleepNormal 0
0
On Mon, Feb 22, 2010 at 9:38 AM, Rick McGuire wrote:
> Ok, I was thinking I'd change to 4.01 first and work through those,
> but your strategy will work better because we have the additional
> ability to trach which fixes have been merged. Don't change a thing.
> Give a yell when you believe you'
Ok, I was thinking I'd change to 4.01 first and work through those,
but your strategy will work better because we have the additional
ability to trach which fixes have been merged. Don't change a thing.
Give a yell when you believe you've finished your triage so I can give
the remaining ones a pas
Rick,
I was just going to post the strategy I am using.
I have a few 'fixe' bugs that I don't want to go into the bug fix
release. So, what I did is:
* Go through all the pending and close everthing that has made it into
a previous release.
* Change the group on all the pending that were left
Mark,
Thank you for going through and doing the updates on the bug status.
The 4.0 ones really should have been closed right when 4.0 went gold.
Sorry about that oversight.
For all of the bug fixes tagged with "Next release", I sort of used
that one as a holding pattern rather than targeting thos
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.
--
Brandon Cherry
Network Engineer, Safe Data, Inc.
(910) 285-
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?
Secondly, what are the values of other and otherObj? I'm most
interested at this point in w
Running from trunk rev 5561.
Error:
Unhandled exception at 0x0036c80c (rexx.dll) in rexx.exe: 0xC005:
Access violation reading location 0x7fd7.
Threads:
0 672 Main Thread Main Thread mainNormal 0
0 1720Worker Thread Win32 Thread7c9
13 matches
Mail list logo
