#24 clg3 problem with signal handling vg-3.1.svn

open
nobody
5
2005-09-22
2005-09-22
No

I recently found clg3 sources which I would like to use
with current valgrind development version.
There is no problem building and running this module,
except for the following problem: if the process being
traced does fork() than receives SIGCHLD, subsequent
output dump would abort with access violation report.
I managed to workaround this problem by commenting out
signal handler setup in clg3/src/main.c
Is this a know problem or incompatibility?

Linux gentoo, x86_86 in 64-bit mode, glibc-2.3.5
Callgrind-0.9.13-VG30-alpha
Using LibVEX rev 1404
Using valgrind-3.1.SVN (r4714)

----begin diff---
--- src/main.c 14 Sep 2005 22:16:33 -0000 1.13
+++ src/main.c 22 Sep 2005 06:08:43 -0000
@@ -966,8 +966,8 @@
CLG_(post_syscalltime));

VG_(track_thread_run) ( & CLG_(run_thread) );
- VG_(track_pre_deliver_signal) ( & CLG_(pre_signal) );
- VG_(track_post_deliver_signal) ( &
CLG_(post_signal) );
+// VG_(track_pre_deliver_signal) ( &
CLG_(pre_signal) );
+// VG_(track_post_deliver_signal) ( &
CLG_(post_signal) );

/* for data collection */
VG_(track_new_mem_startup)(CLG_(my_new_mem_startup));
----end diff-----

Discussion


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks