[Vm-dev] COG crashing - more info
Bob Arning
arning315 at comcast.net
Mon Jan 9 21:55:10 UTC 2012
The most recent crash was with Cog 2522 which I just downloaded a day or
two ago. FWIW, I'm not actually seeing these message on a console - I
locate the files manually after the fact. I'm not very console oriented.
Cheers,
Bob
On 1/9/12 4:05 PM, Eliot Miranda wrote:
>
>
>
>
>
> On Sun, Jan 8, 2012 at 4:20 PM, Bob Arning <arning315 at comcast.net
> <mailto:arning315 at comcast.net>> wrote:
>
>
> Does it take something special to generate one of those? The most
> recent I have is 18 months old.
>
>
> They're produced either when the VM experiences a fatal error (either
> an internal call of error or catching a fatal signal etc). How
> up-to-date is your VM? That you're seeing messages on the console and
> not getting a crash.dmp might indicate your VM is old.
>
>
> Cheers,
> Bob
>
> On 1/8/12 6:34 PM, Eliot Miranda wrote:
>>
>>
>>
>>
>>
>> On Sat, Jan 7, 2012 at 6:22 PM, Bob Arning <arning315 at comcast.net
>> <mailto:arning315 at comcast.net>> wrote:
>>
>>
>> Is that the first file I posted, or yet another file? I
>> looked and did not see anything specifically named "crash.log"
>>
>>
>> Oops. It is called crash.dmp and is produced in whatever the
>> image file's directory is (a poor choice in certain
>> circumstances, but it has to go somewhere).
>>
>>
>> Cheers,
>> Bob
>>
>> On 1/7/12 6:35 PM, Eliot Miranda wrote:
>>> BTW, the below is not as useful as the crash.log file.
>>>
>>
>>
>>
>>
>> --
>> best,
>> Eliot
>>
>
>
>
>
> --
> best,
> Eliot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20120109/b9bf4d43/attachment.htm
More information about the Vm-dev
mailing list