That looks very similar to the top of the crashed thread I saw: 0 rbframework.dylib 0x00a40c59 DebuggerConnection::TransferEncodeString(string) + 175 1 rbframework.dylib 0x00a54fed RuntimeDebuggerShutdown + 17627 2 rbframework.dylib 0x00a55f88 RuntimeDebuggerShutdown + 21622
I also have not been able to reproduce it, but I included the crash log with my report on the stepping problem since it was at least somewhat related. On 4/5/07, 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. > > Charles Yeomans > > On Apr 5, 2007, at 6:14 PM, Dennis Birch wrote: > > > Have you noticed any pattern? I wonder if it has to do with RB's > > constantly increasing memory demands. It seems like it might be > > happening more the longer I use the IDE between relaunches, but I have > > nothing more to go on than my gut feeling. > > > > I also noticed that when it gets into a non-responsive state, I can > > type Command-R to resume running the project, but then the running > > debug application is non-responsive, and it seems to have been donated > > a "Project" menu from the debugger which is highlighted (but not > > responsive). > > > > On 4/5/07, Charles Yeomans <[EMAIL PROTECTED]> wrote: > >> I've suffered about ten debugger-related crashes this afternoon. > >> > >> Charles Yeomans > >> > >> > >> On Apr 5, 2007, at 5:53 PM, Dennis Birch wrote: > >> > >>> I hope I'm not the only one experiencing this. I have been running > >>> into repeated problems with the debugger no longer responding to my > >>> keystrokes to step through code in the middle of a debugging > >>> session. > >>> When this happens, the menu items for stepping through code are > >>> disable as well. I have also experienced at least one crash in the > >>> debugger when stepping through code. > >>> > >>> Since I haven't yet learned how to write perfect code that never > >>> needs > >>> debugging, I find this rather frustrating. If you're experiencing > >>> similar problems, please add your voice to this bug report: > >>> > >>> <http://support.realsoftware.com/feedback/viewreport.php? > >>> reportid=oavefksf> > >>> _______________________________________________ > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
