--- coregrind/vg_proxylwp.c~ Mon Aug 23 15:47:33 2004
+++ coregrind/vg_proxylwp.c Mon Aug 23 15:48:42 2004
@@ -596,6 +596,8 @@
static const vki_kstack_t ss = { .ss_flags = VKI_SS_DISABLE };
#if __FreeBSD__ == 5
+ VG_(message)(Vg_UserMsg, Locking#1 mutex %p/%p, px-mutex,
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
Miguel Mendez wrote:
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
On Mon, 23 Aug 2004 22:03:39 +0200
Simon Barner [EMAIL PROTECTED] wrote:
Hi,
there is a closed problem report in the database:
http://www.freebsd.org/cgi/query-pr.cgi?pr=68992
At the end of that PR, there is a patch that seems to work around
the problem. Could you please test it?
In the last episode (Aug 23), Simon Barner said:
Miguel Mendez wrote:
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
In the last episode (Aug 23), Dan Nelson said:
--- coregrind/vg_proxylwp.c~ Mon Aug 23 15:47:33 2004
+++ coregrind/vg_proxylwp.c Mon Aug 23 15:48:42 2004
And of course I screwed up the patch. The first argument of each print
call should be printing px-mutex, not px-mutex. Here's better
6 matches
Mail list logo
