search

dparnell / strongtalk

Automatically exported from code.google.com/p/strongtalk
0 stars 0 forks source link

smalltalk-side stack traces and infinite process creation #35

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
If printing a value (evaluating #printString) generates an error, then the
system will attempt to show a stack trace, and when evaluating the value,
it's trigger the error ... and creates new processes over and over

There are many ways to provoke this bug. For instance, you can implement
#printString on Test

Test>>printString

  ^1+'a' "this obviously fails"

in a workspace, "Test new", showIt will trigger the bug

Original issue reported on code.google.com by prunedt...@gmail.com on 2 May 2007 at 3:32

GoogleCodeExporter commented 9 years ago 
a quick hack to mitigate the annoyance of this bug : return ^col in
#buildBareVisualTop: before you fill it with activation outliners.

It disables the ST-level stack traces, but you can still kill processes and 
transfert
to the console debugger. (ST-level stack traces are unstable anyway)

Original comment by prunedt...@gmail.com on 3 May 2007 at 12:33