The reference to libc-2.3.6.so just means that spamdyke is crashing
while calling a library function. The segfault message would probably
include the name of the function if libc had been compiled with
debugging symbols included. Since those symbols are not available, the
message can only give the address of the function within the library
file. However, if my (latest) theory about these crashes is correct,
the library function is memcpy(), which copies a block of data from one
location to another in memory. Also, your server is crashing at address
0 as well, it just prints it in a different format ("0000000000000000").
I don't _know_ if this is the same bug, I just _hope_ that it is. :)
-- Sam Clippinger
David Stiller wrote:
> A little difference to my system is that he'd been told that the
> segfaults occur in libc-2.3.6.so, but also
> 0-Addresses. Do you think it's the same bug he hits, does it help us
> with my server? Looking forward
> to getting this bug! :-)
>
>
> Sam Clippinger schrieb:
>
>> Without more information, I would guess that these errors are very
>> likely caused by the same bugs that have been plaguing David Stiller on
>> SLES 10.1 64-bit. I've been working with David for several weeks to
>> identify the source of the crashes and I believe I've finally done it.
>> The latest beta version (published on the spamdyke-dev mailing list
>> today) contains the (latest) fix.
>>
>> If you are so inclined, you could install the latest beta version of
>> spamdyke and see if it solves your issue. Otherwise, upgrade to 4.0.5
>> as soon as it is available (hopefully soon) and report back if you still
>> see segmentation faults.
>>
>> If you want to collect more information with the version you're using,
>> you can do this:
>> 1) From the command line, run "spamdyke -v" and look for
>> "+EXCESSIVE" after the version number. If it's not there, rerun
>> spamdyke's configure script with the "--with-excessive-output" option,
>> then rerun "make". Install the resulting binary.
>> 2) Add the "full-log-dir" option to your configuration file.
>> 3) Wait for another segmentation fault
>> 4) Find the log file(s) produced by the crashed spamdyke(s) and
>> email them to me. I'll examine them to see if your crashes look
>> different than the ones I've been chasing.
>>
>> -- Sam Clippinger
>>
>> Thiago Cesar wrote:
>>
>>
>>> Hi for all, Iam using Debian, with qmail and spamdyke and in my log I seen
>>> something like these:
>>> spamdyke[3729]: segfault at ffffffff9614a818 ip 7f8e8de792a6 sp
>>> 7fff96146728 error 4 in libc-2.3.6.so[7f8e8de05000+121000]
>>> spamdyke[26710]: segfault at 0 ip 7fa7f9a1c03b sp 7fff01cec2c8 error 4 in
>>> libc-2.3.6.so[7fa7f99a8000+121000]
>>> spamdyke[30603]: segfault at 0 ip 7f564d17d076 sp 7fff5544ca28 error 4 in
>>> libc-2.3.6.so[7f564d109000+121000]
>>> spamdyke[32070]: segfault at ffffffffff812ed8 ip 7f7ef753f2a6 sp
>>> 7fffff80ede8 error 4 in libc-2.3.6.so[7f7ef74cb000+121000]
>>> spamdyke[11483]: segfault at 0 ip 7fe0fa2b109e sp 7fff0257eb58 error 4 in
>>> libc-2.3.6.so[7fe0fa23d000+121000]
>>> spamdyke[7549]: segfault at 0 ip 7fa12cee403b sp 7fff351b3788 error 4 in
>>> libc-2.3.6.so[7fa12ce70000+121000]
>>> spamdyke[8630]: segfault at 0 ip 7fa10f00b054 sp 7fff172da8b8 error 4 in
>>> libc-2.3.6.so[7fa10ef97000+121000]
>>> spamdyke[25503]: segfault at 0 ip 7f4eff92a09e sp 7fff07bfa1d8 error 4 in
>>> libc-2.3.6.so[7f4eff8b6000+121000]
>>> spamdyke[13349]: segfault at fffffffff272fdf8 ip 7fa5ea45e25f sp
>>> 7ffff272bd08 error 4 in libc-2.3.6.so[7fa5ea3ea000+121000]
>>>
>>> if anybody can help me will be gracefull, the strange is the spamdyke
>>> continue working, but Iam see these on the log.
>>> Thanks for all,
>>> Thiago Cesar
>>> Diretor TI
>>> MSN: [EMAIL PROTECTED]
>>> Skype: thiago_ceor
>>> -----------------------------------------------
>>> http://www.kionux.com.br
>>> Kionux Soluções em Internet LTDA.
>>> Rua Padre Montoya, 581 sala 02 CEP: 85850-000
>>> Foz do Iguaçu - PR
>>> Telefone: +55 (45) 3025-5864 / 3027-5864
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> spamdyke-users mailing list
>>> [email protected]
>>> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>>>
>>>
>>>
>> _______________________________________________
>> spamdyke-users mailing list
>> [email protected]
>> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>>
>>
>
> _______________________________________________
> spamdyke-users mailing list
> [email protected]
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
