On 4/5/07 6:26 PM, "Charles Yeomans" <[EMAIL PROTECTED]> wrote:

> The only pattern I've noticed is that if I take too long to step
> through the code, the app ends up crashing.  The crash log is pretty
> much always the same - -
> 
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000005
> 
> Thread 0 Crashed:
> 0   rbframework.dylib                0x01057fd8 RuntimeDebuggerShutdown
> + 17606
> 1   rbframework.dylib                0x01058f88 RuntimeDebuggerShutdown
> + 21622
> 2   rbframework.dylib                0x0105a76b
> DSDelegate::DebuggerConnectionMessage(string, string) + 47
> 3   rbframework.dylib                0x01043d3a
> DebuggerConnection::DelegateMessage(string, string) + 116
> 4   rbframework.dylib                0x01044a19
> TCPSocketConnection::SocketDataReceived(TCPSocket*) + 565
> 5   rbframework.dylib                0x010605b4 TCPSocket::FireEvents()
> + 156
> 6   rbframework.dylib                0x01038538 TCPSocketPosix::Poll() +
> 1278
> 7   rbframework.dylib                0x0104d9b0 DoNetIdle(unsigned char)
> + 160
> 8   rbframework.dylib                0x010e6b46 NetIdle + 40
> 9   rbframework.dylib                0x0105ac83
> DSDelegate::DebuggerConnectionClosed() + 1265
> 10  rbframework.dylib                0x0105ad35
> DSDelegate::DebuggerConnectionClosed() + 1443
> 11  rbframework.dylib                0x0105b24c DebuggerHook + 432
> 
> But I cannot reproduce it, or of course I would have reported it.

If the OS X-using engineers at RS are experiencing this, I can't imagine
that it will be tolerated for very long.

I can't speculate on the likelihood of a special release.

It's old news now, but knowing they're using the same IDE we are ---- it
feels good.  :-)  We are *all* in the same boat.

-- 
Russ Tyndall
Wake Forest, NC



_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to