|
From: Dirk M. <dm...@gm...> - 2006-01-10 13:12:14
|
On Tuesday 10 January 2006 13:59, Keith Mange wrote:
> The application normally takes a few seconds to load. I gave it 4 hours
> running under valgrind before giving up.
Ok, then it probably really hung somewhere. strace/ltrace telling something?
does an attached gdb produce a sensible backtrace (most likely not, but it
would be worth a try).
then you either have to figure out how to reduce it to a small code snippet
that reproduces the valgrind lockup or try to look through the valgrind debug
output to see if you can find something obvious on why it locks up. see
valgrind --help-debug output:
--sanity-level=<number> level of sanity checking to do [1]
--profile=no|yes profile? (tool must be built for it) [no]
--trace-flags=<XXXXXXXX> show generated code? (X = 0|1) [00000000]
--profile-flags=<XXXXXXXX> ditto, but for profiling (X = 0|1) [00000000]
--trace-notbelow=<number> only show BBs above <number> [0]
--trace-syscalls=no|yes show all system calls? [no]
--trace-signals=no|yes show signal handling details? [no]
--trace-symtab=no|yes show symbol table details? [no]
--trace-cfi=no|yes show call-frame-info details? [no]
--trace-sched=no|yes show thread scheduler details? [no]
--wait-for-gdb=yes|no pause on startup to wait for gdb attach
--command-line-only=no|yes only use command line options [no]
Also, try if "valgrind --tool=none" works for your application. that would be
very important to know.
Dirk
|