Hi! El mar., 16 de jun. de 2015 a la(s) 8:55 a. m., Peter Uhnák < i.uh...@gmail.com> escribió:
> I ended up fileouting what I could in headless mode (had utf8 issues for > whatever reason so I didn't get it all), and rewriting the rest. :/ > But what happens once will happen again... so some more generic solution > for this would be nice. > > Given command line was usable you could have used it to break the loop. Let's say you had your method that recurses looks like BadGuy>>recursive self recursive then you can do ./pharo eval "BadGuy compile: 'recursive'" that will break your method but will help you recover the rest :) Another useful debugging tool, maybe you knew about it, is sending the SIGUSR1 signal to the VM process. It will print out the stack and help you detect possible problems. Yuriy mentioned Oz, and it looks viable, provided it works with current > pharo version and is capable of dealing with (most likely) corrupted memory. > Well, Oz has never left the prototype stage, and I doubt it will soon with the time I have and the hackish VM requirements. Guille
