|
From: Greg C. <gre...@ya...> - 2008-03-26 05:52:46
Attachments:
pyvalgrind-listener.py
|
Hi all,
Has anyone tried to create their own custom valgrind-listener? The attached python script was the first attempt at having valgrind attach to it.
But the valgrind fails to connect.
==11618== valgrind: failed to connect to logging server 'X.X.X.X:1500' -3.
==11618== Log messages will sent to stderr instead.
I modified the valgrind code to show that -3 is a failure in my_connect.
The regular valgrind-listener works fine.
Does anybody have any suggestions or tips?
FYI:
Primary build target: AMD64_LINUX
Secondary build target: X86_LINUX
Thanks in advance.
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping |
|
From: Ashley P. <api...@co...> - 2008-03-26 12:44:21
|
On Tue, 2008-03-25 at 22:52 -0700, Greg Czajkowski wrote: > Hi all, > > Has anyone tried to create their own custom valgrind-listener? The > attached python script was the first attempt at having valgrind attach > to it. I wrote one a year or so ago in perl and it worked fine. > But the valgrind fails to connect. > ==11618== valgrind: failed to connect to logging server 'X.X.X.X:1500' > -3. > ==11618== Log messages will sent to stderr instead. The most common problem is binding to 127.0.0.1 instead of * when binding to the socket are you running on a single host, what does telnet X.X.X.X 1500 tell you? Ashley, |