When I run a real program valgrind hangs on my redhat desktop, however I
can run on other systems with the same executable.
I ran
valgrind -v -v -v -d -d -d myprog.exe
and it spits out a lot of output and then sits there for many minutes,
I've let it sit for overnight and no progress.
I'm guessing some system configuration, but I googled and looked around
and didn't see anything that could cause this..
The last set of output is below, but it doesn't lend any clue to me..
--2921-- di_notify_mmap-4: noting details in DebugInfo* at 0x100920A7E0
--2921-- di_notify_mmap-5: achieved accept state for
/projects/sems/install/rhel7-x86_64/sems/compiler/gcc/7.2.0/openmpi/1.10.1/lib/openmpi/mca_grpcomm_bad.so
--2921-- Reading syms from
/projects/sems/install/rhel7-x86_64/sems/compiler/gcc/7.2.0/openmpi/1.10.1/lib/openmpi/mca_grpcomm_bad.so
--2921-- svma 0x0000000e10, avma 0x002fe04e10
--2921-- cfsi range rx-mappings coverage check: Covered
0x0-0xffffffffffffffff
--2921-- di_notify_mmap-0:
--2921-- di_notify_mmap-1: 0x30007000-0x30807fff rw-
--2921:1: aspacem allocated valgrind thread stack at 0x100abec000 size
1064960
--2921:2: stacks register [start-end] [0x30008000-0x30806FFF] as stack 1
--2921:1:syswrap- run_a_thread_NORETURN(tid=2): pre-thread_wrapper
--2921:1:syswrap- thread_wrapper(tid=2): entry
--2921-- di_notify_mmap-0:
--2921-- di_notify_mmap-1: 0x4022000-0x4026fff rw-
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
