|
From: | Paolo Bonzini |
Subject: | Re: [Help-smalltalk] SEGF in gst_initialize |
Date: | Sun, 01 Nov 2009 00:44:13 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4 |
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
[Prev in Thread] | Current Thread | [Next in Thread] |