On Mon, 21 Okt 2002, Till Krech wrote:

> Linux)" The message goes to stderr, so it's very difficult to see it (see 
> above) ;-)

I see :)

> > How does it load it ? with dlopen? valgrind should be able to survive that.
> yeah. it even runs konqueror itself with all these gimmicks in shared 
> libraries ;)

Ok, I've asked Julian and he has no idea either. can you do a 
--trace-syscalls=yes to see which syscalls made it escape the simulated CPU? 
Its most likely a bug somewhere in valgrind. 


-- 
Dirk (received 394 mails today)