|
From: Greg C. <gre...@ya...> - 2008-03-26 19:27:01
Attachments:
pyvalgrind-listener.py
|
Thanks Ashley,
That did it! Instead of binding to 127.0.0.1, binding to the hosts IP allowed connections to happen. Binding to '*' or '*.*.*.*' wasn't liked by python. Nevertheless the attached example is a simple echo script.
My goal is to create a divergence function trace comparator tool which takes two binaries, runs them through --tool=callgrind --ct-verbose=1 and determines when they diverge. If anyone is interested I can post it to the list when it's ready.
Since the amount of data coming from callgrind in this usage model in some cases is GBs, a lot of filtering and pruning needs to happen.
Gregory
----- Original Message ----
From: Ashley Pittman <api...@co...>
To: Greg Czajkowski <gre...@ya...>
Cc: val...@li...
Sent: Wednesday, March 26, 2008 7:44:14 AM
Subject: Re: [Valgrind-users] custom valgrind-listener
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,
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ |
|
From: Greg C. <gre...@ya...> - 2008-03-26 20:58:57
|
> Are you running the two programs at the same time then? Otherwise you
> are going to need to buffer at least one of them.
>
> Ashley,
Yes, actually both will be buffered and a separate thread will consume both buffers.
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs |
|
From: Ashley P. <api...@co...> - 2008-03-26 20:35:41
|
On Wed, 2008-03-26 at 12:26 -0700, Greg Czajkowski wrote: > Thanks Ashley, > > That did it! Instead of binding to 127.0.0.1, binding to the hosts IP > allowed connections to happen. Binding to '*' or '*.*.*.*' wasn't > liked by python. Nevertheless the attached example is a simple echo > script. I think the standard is to use 0.0.0.0 as a wildcard, socket programming is not my forte however. > My goal is to create a divergence function trace comparator tool which > takes two binaries, runs them through --tool=callgrind --ct-verbose=1 > and determines when they diverge. If anyone is interested I can post > it to the list when it's ready. > > Since the amount of data coming from callgrind in this usage model in > some cases is GBs, a lot of filtering and pruning needs to happen. Are you running the two programs at the same time then? Otherwise you are going to need to buffer at least one of them. Ashley, |