|
From: Tom H. <to...@co...> - 2006-01-16 08:55:33
|
In message <ABD...@br...>
Richard Frith-Macdonald <ri...@br...> wrote:
> Unfortunately, valgrind doesn't seem to work with Sun's Java
> implementation. After much searching the 'resolved' bug #69508 seems
> to describe what is happening ... the last two comments in the bug
> report talk about Java re-execing to put its own directory at the
> front of LD_LIBRARY_PATH and valgrind doing the same ... getting into
> an infinite loop.
Possibly - if you use --trace-children=yes do you see a whole stream
of valgrind startup messages appearing?
> I guess the bug being marked as 'resolved' refers to the original
> problem (a 'stack size too small' report) ... but it doesn't actually
> explain how to get valgrind/java to work together. has this actually
> been done? Is there a known workaround?
I'm not sure when the bug was resolved, but we no longer change
the value of LD_LIBRARY_PATH as it was only ever needed to allow
us to replace libpthread with our own one and we haven't done that
since the 2.2.x releases.
I think there was a delay in removing the LD_LIBRARY_PATH code, but
the 3.x releases should all be fine - none of them will try and
change it.
What version are you using?
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|