|
From: Jason W. <jp...@im...> - 2004-03-04 05:06:48
|
What could cause this sort of thing? I didn't see anything in the FAQ. I can go into details if there isn't an easy answer. I tried the nVidia CPU env var. -- _ ( \ _ \ /_ / _ _ Jason Weber Oceanside, CA \|(\/)())) \/\/(-/_)(-/( http://www.imonk.com/baboon ba...@im... // we...@ac... (/ ~fe uname -a db cataclysm /mnt/raid Linux cataclysm 2.4.21 #2 Wed Nov 19 21:36:40 PST 2003 i686 GNU/Linux ~fe alias vg db cataclysm /mnt/raid vg='valgrind --leak-check=yes --leak-resolution=low --show-reachable=yes --num-callers=50 --suppressions=/home/symhost/sym/proj/fe/test/test.supp --gdb-path=/usr/bin/gdb --trace-children=yes' ~fe vg ~fe/lib/x86_linux_debug/xViewer.exe 1 db cataclysm /mnt/raid ==6872== Memcheck, a memory error detector for x86-linux. ==6872== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==6872== Using valgrind-2.1.0, a program supervision framework for x86-linux. ==6872== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==6872== Estimated CPU clock rate is 996 MHz ==6872== For more details, rerun with: -v ==6872== Registry::manage("fexViewerDL") openDL OVERLAPPING EXE SEGMENTS new: start 0x420C2000, size 453484 old: start 0x42126000, size 32768 valgrind: vg_memory.c:94 (add_exe_segment_to_list): Assertion `! overlap' failed. ==6872== at 0x4017A08D: vgPlain_skin_assert_fail (vg_mylibc.c:1102) ==6872== by 0x4017A08C: assert_fail (vg_mylibc.c:1098) ==6872== by 0x4017A11B: vgPlain_core_assert_fail (vg_mylibc.c:1109) ==6872== by 0x401778EA: add_exe_segment_to_list (vg_memory.c:94) ==6872== by 0x401779AD: vgPlain_new_exeseg_mmap (vg_memory.c:129) ==6872== by 0x4018A944: mmap_segment (vg_syscalls.c:151) ==6872== by 0x40192C75: after_mmap (vg_syscalls.c:3271) ==6872== by 0x40196D84: vgPlain_post_syscall (vg_syscalls.c:4948) ==6872== by 0x40158308: sched_do_syscall (vg_scheduler.c:697) ==6872== by 0x40158BC2: vgPlain_scheduler (vg_scheduler.c:1135) ==6872== by 0x4017470A: vgPlain_main (vg_main.c:1679) sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==6872== at 0x4001139D: (within /lib/ld-2.3.2.so) ==6872== by 0x400064A5: _dl_map_object (in /lib/ld-2.3.2.so) ==6872== by 0x4000AA18: (within /lib/ld-2.3.2.so) ==6872== by 0x4000BF25: _dl_catch_error (in /lib/ld-2.3.2.so) ==6872== by 0x4000B490: _dl_map_object_deps (in /lib/ld-2.3.2.so) ==6872== by 0x405CAC9F: (within /lib/libc-2.3.2.so) ==6872== by 0x4000BF25: _dl_catch_error (in /lib/ld-2.3.2.so) ==6872== by 0x405CB438: _dl_open (in /lib/libc-2.3.2.so) ==6872== by 0x4024E007: (within /lib/libdl-2.3.2.so) ==6872== by 0x4000BF25: _dl_catch_error (in /lib/ld-2.3.2.so) ==6872== by 0x4024E4C5: (within /lib/libdl-2.3.2.so) ==6872== by 0x4024E053: dlopen (in /lib/libdl-2.3.2.so) ==6872== by 0x40255309: fe::DL_Loader::openDL(fe::String, int) (DL_Loader.cc:58) ==6872== by 0x402BB577: fe::Registry::manage(fe::String const&) (Registry.cc:214) ==6872== by 0x804CE52: main (xViewer.cc:35) Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: valgrind.kde.org In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. zsh: exit 1 valgrind --leak-check=yes --leak-resolution=low --show-reachable=yes 1 ~fe 1 db cataclysm /mnt/raid |