Re: [Pharo-project] Debugging aids
Stef, Will do. The append option will come first. The crash dumps might take more effort, since I did not even see the feature on Linux. Not sure what to make of that. I guess I was hacking the VM, so maybe it is available only on Windows. If that is the case, we should fix it. I assume you want an option? How about #appendToDebugLog? I will confess to thinking (if only to myself) this should simply be the behavior, but the option route works too. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab@anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029
stephane.ducasse@inria.fr 9/5/2008 11:02:06 AM >>> send us the code :)
stef On Sep 5, 2008, at 5:45 PM, Bill Schwab wrote:
Hello all,
Random thoughts/wishes:
The UI discussion reminded me of a couple of things. Squeak appears
to overwrite its debug log; minimally, I think there should be an option to append, and it probably should default to true. Many times, I've had what our British friends would call a knock-on effect overwrite the trace of the real cause of the problem. The same should apply to the crash dump.
The option to show call stacks (which I am not seeing on the Linux VM, and would like to<g>), should show all non-dead threads, not simply
the active thread. IIRC, there has been some progress on that front.
Bill
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bschwab@anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (1)
-
Bill Schwab