Thanks again -- that is definitely a useful page at unixville. BTW from the dump I got from your previous suggestion I think that my original bug wasn't a loop after all, but was instead caused by exponentially growing BigIntegers. We'll see, but at least I have a better way to investigate things now.
-Lee On Mar 17, 2010, at 2:58 PM, Richard Newman wrote: >> It'd still be even nicer to be able to get some info without quitting, but >> this is definitely an improvement! > > The JVM shouldn't quit when it gets a SIGQUIT. That's just the signal name. > > You might find this useful: > > http://www.unixville.com/~moazam/stories/2004/05/18/debuggingHangsInTheJvm.html > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- Lee Spector, Professor of Computer Science School of Cognitive Science, Hampshire College 893 West Street, Amherst, MA 01002-3359 lspec...@hampshire.edu, http://hampshire.edu/lspector/ Phone: 413-559-5352, Fax: 413-559-5438 Check out Genetic Programming and Evolvable Machines: http://www.springer.com/10710 - http://gpemjournal.blogspot.com/ -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
