|
From: Brendan H. <har...@ya...> - 2005-09-19 12:57:02
|
Hi I am using Helgrind (part of valgrind 2.2.0) to assist with ensuring that processes are thread safe. I am find ing that for many (although not all) the process crashes shortly after startup with the message 'segmentation fault' (last lines from trace shown below): --7478-- supp: 1 _dl_lookup_symbol_x/fixup/_dl_runtime_resolve ==7478== ==7478== IN SUMMARY: 24 errors from 24 contexts (suppressed: 1 from 1) ==7478== ==7478== 25 possible data races found; 0 lock order problems --7478-- TT/TC: 0 tc sectors discarded. --7478-- 97133 tt_fast misses. --7478-- translate: new 32065 (532860 -> 4505112; ratio 84:10) --7478-- discard 0 (0 -> 0; ratio 0:10). --7478-- chainings: 17647 chainings, 0 unchainings. --7478-- dispatch: 29121137 jumps (bb entries); of them 7666969 (26%) unchained. --7478-- 14665/395268 major/minor sched events. --7478-- reg-alloc: 86 t-req-spill, 793027+202 orig+spill uis, --7478-- 80042 total-reg-rank --7478-- sanity: 14659 cheap, 587 expensive checks. --7478-- ccalls: 168577 C calls, 60% saves+restores avoided (596770 bytes) --7478-- 221736 args, avg 0.61 setup instrs each (169998 bytes) --7478-- 0% clear the stack (505314 bytes) --7478-- 139 retvals, 47% of reg-reg movs avoided (128 bytes) Segmentation fault Looking at the messages I think that the crash has occured reasonable early on during the intialisation. I am using the command below to run process: valgrind -v --tool=helgrind <process name> and am running it on SUSE 9.0 enterprise (linux). Does anybody have an idea what could be causing this or any suggestions on what to try. Thanks __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |