On 07/09/12 08:35 +0300, Vladislav Bogdanov wrote:
Hi, sorry for posting to this ML, not libqb one, it is just one-shot note, and subscribing to that ML seems to be too much for just one message.
Should be fixed in the next release: https://github.com/asalkeld/libqb/commit/b79f8ceb1e5e691906878c1c39eca7c2b5420224 -Angus
valgrind reports following error (while analyzing pacemaker binaries): ==1737== Syscall param socketcall.sendto(msg) points to uninitialised byte(s) ==1737== at 0x7AE6002: send (in /lib64/libc-2.12.so) ==1737== by 0x869FE7F: qb_ipc_us_send (in /usr/lib64/libqb.so.0.13.0) ==1737== by 0x86A0FE5: qb_ipcc_us_setup_connect (in /usr/lib64/libqb.so.0.13.0) ==1737== by 0x869DD33: qb_ipcc_connect (in /usr/lib64/libqb.so.0.13.0) ==1737== by 0x5885459: crm_ipc_connect (ipc.c:341) ==1737== by 0x589DC27: mainloop_add_ipc_client (mainloop.c:613) ==1737== by 0x545C842: cib_native_signon_raw (cib_native.c:222) ==1737== by 0x41802D: do_cib_control (cib.c:167) ==1737== by 0x407726: s_crmd_fsa_actions (fsa.c:315) ==1737== by 0x408D85: s_crmd_fsa (fsa.c:250) ==1737== by 0x4109CD: crm_fsa_trigger (callbacks.c:251) ==1737== by 0x589C3C2: crm_trigger_dispatch (mainloop.c:105) ==1737== by 0x81DAF0D: g_main_context_dispatch (in /lib64/libglib-2.0.so.0.2200.5) ==1737== by 0x81DE937: ??? (in /lib64/libglib-2.0.so.0.2200.5) ==1737== by 0x81DED54: g_main_loop_run (in /lib64/libglib-2.0.so.0.2200.5) ==1737== by 0x404D9D: crmd_init (main.c:139) ==1737== by 0x7A1BCDC: (below main) (in /lib64/libc-2.12.so) ==1737== Address 0x7feffd514 is on thread 1's stack Problem (not really problem but it is annoying) is that valgrind thinks that qb_ipcc_us_setup_connect() does not initialize request variable (because of aligned(8) but structure is 12 bytes ?) before passing it to qb_ipc_us_send as a message buffer. Architecture is x86_64. 0.14.1 has the same code. Best regards, Vladislav _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
