Hi all, Is anybody using valgrind on 5.3BETA1 or newer? I've been using it for a while on 5.2.1 without any problems, until I upgraded my system to RELENG_5. The program works but it never exits after running your program, it gets stuck into `umtx' state indefinitely. This is happening with both plain jane valgrind and valgrind-snapshot ports. Is this already a known issue?
I've tried to attach to the valgrind (built with -g) process with gdb,
but the backtrace doesn't give much info...
Attaching to program: /usr/local/bin/valgrind, process 24554
0xb803cf79 in ?? ()
(gdb) bt
#0 0xb803cf79 in ?? ()
#1 0xb803082f in ?? ()
#2 0xb82e4f78 in ?? ()
#3 0xb82e4f64 in ?? ()
[...]
#49 0x08048000 in ?? ()
#50 0x080497d0 in setrlimit ()
#51 0xb81e1030 in ?? ()
[...]
#56 0xb81df0a0 in ?? ()
#57 0x08048430 in fix_auxv (v_init_esp=0x1, info=0x1) at stage1.c:124
Previous frame inner to this frame (corrupt stack?)
Cheers,
--
Miguel Mendez <[EMAIL PROTECTED]>
http://www.energyhq.es.eu.org
PGP Key: 0xDC8514F1
Note: All HTML and non-english mail goes to /dev/null
pgpNMLpLB7ZrR.pgp
Description: PGP signature
