Re: [syslog-ng] (syslog-ng): unaligned access: (SOLVED)
pid 29068 (syslog-ng): unaligned access: va=0x14001645c pc=0x12001b2b0 ra=0x12001b2b0 op=stt pid 29068 (syslog-ng): unaligned access: va=0x14001644c pc=0x12001b018 ra=0x12001b018 op=stq pid 29068 (syslog-ng): unaligned access: va=0x140016454 pc=0x12001b028 ra=0x12001b028 op=stt pid 29068 (syslog-ng): unaligned access: va=0x140016454 pc=0x12001b030 ra=0x12001b030 op=ldq pid 29068 (syslog-ng): unaligned access: va=0x14001644c pc=0x12001b040 ra=0x12001b040 op=ldq 0x12000f3f0 288 conn->queue_node =
I've got this one, it's caused by the optional malloc debugger which was errouneously included even in --with-debug was not given (it was not 64bit clean). The new libol version 0.2.17 should fix this. http://www.balabit.hu/downloads/libol/0.2/libol-0.2.17.tar.gz -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
Baszi, I'm sorry to say that I'm still getting unaligned traps for each log entry under Alpha-Linux, as described previously. I've built libol 0.2.17 and syslog-ng 1.4.4 with and without debugging, and the results are the same. Unfortunately I don't know how to cause the application to core when it hits the trap, and haven't been able to find out. If I can generate a core, I'll backtrace it and send it on to you.
I've got this one, it's caused by the optional malloc debugger which was errouneously included even in --with-debug was not given (it was not 64bit clean). The new libol version 0.2.17 should fix this.
http://www.balabit.hu/downloads/libol/0.2/libol-0.2.17.tar.gz
--
Thanks, Ger.
participants (2)
-
Balazs Scheidler
-
ger