cyrus-murder problems with database corruption in the frontend/master

João Assad jfassad at
Thu Apr 7 15:29:12 EDT 2005

Derrick J Brashear wrote:

> On Wed, 6 Apr 2005, João Assad wrote:
>>> and then give us a backtrace from the core which you will then get?
>> After doing that, the mupdate process now exits with signal 11 as 
>> expected.
>> OTOH the core isnt getting dumped to disk for some reason...
> The only internal resource limit play happens for fds, not coredumps, 
> so we haven't disabled it, if you can't get a core, I'm somewhat lost 
> as to suggestions.

Ok I got a backtrace ( I think ) . I dont really know how to use gdb

Core was generated by `mupdate -m'.
Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0xb7fa4000
#0  0x005067ce in ?? ()
(gdb) thread apply all bt full

Thread 302 (process 17362):
#0  0x004b57a2 in ?? ()
No symbol table info available.
Cannot access memory at address 0xbff1b304
#0  0x005067ce in ?? ()

(gdb) i reg
eax            0x0      0
ecx            0xa12f7a4f       -1590724017
edx            0xa12f7520       -1590725344
ebx            0x5e5fdc 6184924
esp            0xa12f6f00       0xa12f6f00
ebp            0xa12f74fc       0xa12f74fc
esi            0x80fc66c        135251564
edi            0xa12f763c       -1590725060
eip            0x5067ce 0x5067ce
eflags         0x10286  66182
cs             0x73     115
ss             0x7b     123
ds             0x7b     123
es             0x7b     123
fs             0x0      0
gs             0x33     51

Cyrus Home Page:
Cyrus Wiki/FAQ:
List Archives/Info:

More information about the Info-cyrus mailing list