Hal Eden wrote:
> ooh, sounds like a tough one!
>
> you might try turning on debugging and logDebuggerStackToFile in the
> image to see if you get any (squeak) stack traces related to this.
>
cool, thanks, that sounds like i could get more debug info. while i'm at
it, should i enable securityChecksEnabled and/or cpuWatcherEnabled ?
after the swiki is started an running a while cpu load is at 10..20%.
before the squeak process crashes, cpu utilization is right under the
ceiling.
> is there any stack backtrace ("where") available when you use gdb?
the only line i got was > 0x080638c2 in
allocateheaderSizeh1h2h3doFillwith ()
> are you running WinterLong?
it currently is
Squeak 3.7-7 #5989 (bsd ports) :: Comanche 7.0.2 :: Swiki 1.5 on FreeBSD
(but has earlier been running on macOS9, OSX and linux as well).
the symptoms started on the linux box, so i put it onto a bsd box where
it ran for a week before the daily crashing happened again.
i initially activated the image to start on a mac and copied it to the
server (no X forwarding from home and no X on the server) and started it
there.
> what is your disk space like on the partition where the logs are
> written? (i was getting daily crashes a while back and it turned out my
> logs were filling up the partition)
there is still plenty of space, on its original box i leave it running
on a partition with ~10 Gigs of free space, on the box now it is even
more. (it has less ram, though)
i just started it with
-memory 128m -mmap 512m -headless
to see if it makes a difference.
>
> [scratches his head]
>
> hal
>
>
>
cheers,
tee
_______________________________________________
Pws mailing list
[email protected]
https://mailman.cc.gatech.edu/mailman/listinfo/pws
