[this bug might be related to 502208]
Launching gabber resulted in the following error:
gabber 0.8.7.12
gtkspell: Spell command printed on stderr -- probably
failed.
gtkspell: Spell command printed on stderr -- probably
failed.
Neither ispell nor aspell could run, spell-checking
disabled
zsh: abort (core dumped) gabber
But strangely enough, the problem did not occur for all
users on the computer.
I think my core dumps won't help other people :(
Core was generated by `gabber'.
Program terminated with signal 6, Aborted.
#0 0x40ffe3d1 in ?? ()
(gdb) bt
#0 0x40ffe3d1 in ?? ()
#1 0x40fff979 in ?? ()
#2 0x40f7f45c in ?? ()
#3 0x40f7f616 in ?? ()
#4 0x081c09d6 in ?? ()
#5 0x08141309 in ?? ()
#6 0x0813a2e7 in ?? ()
#7 0x0811a299 in ?? ()
#8 0x080fac0d in ?? ()
#9 0x080fa133 in ?? ()
#10 0x08087009 in ?? ()
#11 0x40fed082 in ?? ()
(gdb) quit
Actually, my problem was due to corrupted (?) messages
in spool. Indeed, the error occured in
judo::ElementStream::push(char const*, int)
(this=0xbffff264, data=0xbfffe110 "</spool><message
from='[censored]@aim.ulysse.iie.cnam.fr'
to='decamps@ulysse.iie.cnam.fr/Gabber'><body>hello</body><x
stamp='20030121T18:18:44'
xmlns='jabber:x:delay'/></message></spool><message
from='"..., datasz=579) at ElementStream.cpp:55
Since I have deleted .Gabber-spool, gabber now just
works fine.
Logged In: YES
user_id=9539
Yes, this is a known bug with the Gabber spool. Thanks.