On 11/01/2009 12:09 AM, Roland Plüss wrote:
I can understand that but is it not bad to begin with to cause a SEGF in the first place? It's just that when my apps cause a SEGF at any place red flags come up immediatly.
If you are asking the OS to report writes into the "old generation" by write-protecting pages, the OS has no way to do so but raising a SIGSEGV (or similar exception under Mac OS/Mach and Windows).
Again, that's not a real problem. When a SIGSEGV is really an error and is turned into a SIGABRT, the backtrace is totally recognizable and you get the fault address in the backtrace.
Paolo _______________________________________________ help-smalltalk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-smalltalk
