Hi,

here is just another crash dump.
I have been doing weird things 
(making/unmaking mountpoints, 
 recently purged a volume etc)
So it may not be from a common 
day-byday-routine.

Since I haven't seen this crash before, 
this mail is just as a reminder where
things have gone wrong in the past, 
just in case you work on the code
someday.

Yours,
Steffen

(Who tries to hunt the error that bugs us for several days now,
 recently reported to the list by Eduard)

-----------------------------------------

#0  0x40138c16 in __sigsuspend (set=0x151d1984) at ../sysdeps/unix/sysv/linux/sigsuspend.c:45
#1  0x080b24c0 in SigChoke (sig=11) at sighand.cc:241
#2  <signal handler called>
#3  0x0806eaa6 in fsobj::Open (this=0x52e5f5c8, writep=0, execp=0, truncp=0, cp=0x151d3e20, uid=0) at fso_cfscalls2.cc:91
#4  0x080ac591 in vproc::open (this=0x81fc190, cp=0x151d3e20, flags=1) at vproc_vfscalls.cc:226
#5  0x080b1590 in worker::main (this=0x81fc190) at worker.cc:1327
#6  0x080a72a2 in VprocPreamble (init_lock=0x81fc1d0) at vproc.cc:146
#7  0x400882f0 in Create_Process_Part2 () at lwp.c:796

console.log:
10:19:10 DispatchWorker: signal received (seq = 66557)
10:28:30 Fatal Signal (11); pid 22125 becoming a zombie...
10:28:30 You may use gdb to attach to 22125

venus.log:
[ T(01) : 0198 : 10:27:56 ] BeginRvmFlush (1, 86440, S)
[ T(01) : 0198 : 10:27:56 ] EndRvmFlush
[ W(21) : 0000 : 10:28:09 ] Cachefile::SetLength 1536
[ H(07) : 0004 : 10:28:22 ] HDBDaemon just woke up
[ H(07) : 0005 : 10:28:22 ] HDBDaemon about to sleep on hdbdaemon_sync
[ W(21) : 0000 : 10:28:30 ] *****  FATAL SIGNAL (11) *****