Hi there,
I'm getting some valgrind hits from libev-4.15. It's always with the
ECB_MEMORY_FENCE macro. I've checked both AMD64 and i386, the hits
occur on the i386 version only.
This memory fencing stuff is beyond my knowledge. Is this something
to worry about?
Thanks
==24105== Invalid read of size 1
==24105== at 0x805A0DD: ev_run (ev.c:3311)
==24105== by 0x804B755: main (ev.h:820)
==24105== Address 0xfe89e61f is just below the stack ptr. To
suppress, use: --workaround-gcc296-bugs=yes
==24105==
==24105== Invalid read of size 1
==24105== at 0x80563FF: ev_sighandler (ev.c:2135)
==24105== by 0x6B88287: ??? (in /lib/i386-linux-gnu/libc-2.15.so)
==24105== Address 0xfe89debf is just below the stack ptr. To
suppress, use: --workaround-gcc296-bugs=yes
==24105==
==24105== Invalid read of size 1
==24105== at 0x8056425: ev_sighandler (ev.c:2145)
==24105== by 0x6B88287: ??? (in /lib/i386-linux-gnu/libc-2.15.so)
==24105== Address 0xfe89debf is just below the stack ptr. To
suppress, use: --workaround-gcc296-bugs=yes
==24105==
==24105== Invalid read of size 1
==24105== at 0x8056DCD: pipecb (ev.c:2214)
==24105== by 0x8055F0F: ev_invoke_pending (ev.c:2994)
==24105== by 0x805A72F: ev_run (ev.c:3394)
==24105== by 0x804B755: main (ev.h:820)
==24105== Address 0xfe89e5cf is just below the stack ptr. To
suppress, use: --workaround-gcc296-bugs=yes
==24105==
==24105== Invalid read of size 1
==24105== at 0x8056DE7: pipecb (ev.c:2221)
==24105== by 0x8055F0F: ev_invoke_pending (ev.c:2994)
==24105== by 0x805A72F: ev_run (ev.c:3394)
==24105== by 0x804B755: main (ev.h:820)
==24105== Address 0xfe89e5cf is just below the stack ptr. To
suppress, use: --workaround-gcc296-bugs=yes
==24105==
_______________________________________________
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
