On Aug 22, 2009, at 6:50 PM, Schwab,Wilhelm K wrote: > Hello all, > > I (stupidly) created a runaway recursion that happened to be in a > Seaside app that uses LDAPLayer, and that is currently using drives > shared over a pre-production vpn from a 64 bit Ubuntu system. > Hopefully you won't think less of me for not immediately thinking of > infinite recursion as the cause of the problems. It did what is > IMHO the worst thing a program can do: it just stopped responding. > It makes sense now, and the next time I see the IDE get sluggish and > finally lock up, I will probably think of recursion before looking > for strange causes. As it was, I simply moved breakpoints around > (making liberal use of the End Process button on Ubuntu's system > monitor) until I finally put one in front of something that I > thought should have worked, and in fact was the culprit. > > For good or bad, Dolphin would promptly complain of the callstack > being too deep, after which the mistake is fairly easy to find. I > have never had problems with that limit, but IIRC others have. > Would it be simple to add an optional limit on the stack depth? > Would you do it, or would it be asking for trouble? Is there a less > invasive way to aid in debugging this scenario?
this would be nice because I found myself often impossible to bring a debugger or getting a screen full of wanring windows and I have to kill the image. Improving the debug possibility would be importatn but I have no idea how to address it. > > Bill > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
