perfsonar-user - Re: [perfsonar-user] bwctl OSX giving strange results

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] bwctl OSX giving strange results

From: Brian Candler <>
To: Aaron Brown <>
Cc: Brian Tierney <>, "" <>
Subject: Re: [perfsonar-user] bwctl OSX giving strange results
Date: Sat, 20 Dec 2014 10:58:04 +0000
Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=dBX2Za uQ1Nvw1Joah+WA/Z+DOJDIi+oqFdT+7UBvbzl6cVvTeFOctFKDaXR/yvJ6xEd3d9 DNt8HG4gDeDstymDrtqt9yQVMsjyL2Uiqhb2o1rbkz3OJ8zznVDz91qPJVpuBnfN yO6naph+VzktykA/Ux7Qydk4vsot4PfzAH2vo=

On 19/12/2014 12:47, Aaron Brown wrote:

I’ve run bwctl in valgrind before, but it’s not warned of anything weird

It's turning up some interesting stuff.

==5217== Syscall param write(buf) points to uninitialised byte(s)
==5217== at 0x54462F0: __write_nocancel (syscall-template.S:81)
==5217== by 0x41EF6D: I2Writeni (in /home/brian/perfsonar-ps.bwctl/bwctld/bwctld)
==5217== by 0x408DDE: BWLDReservationQuery (policy.c:1948)
==5217== by 0x40A6E4: BWLDCheckTestPolicy (policy.c:2381)
==5217== by 0x40E942: _BWLCallCheckTestPolicy (context.c:1140)
==5217== by 0x40C686: BWLProcessTestRequest (sapi.c:625)
==5217== by 0x405E53: main (bwctld.c:1385)
==5217== Address 0xffeffca7e is on thread 1's stack
==5217==

Re: [perfsonar-user] bwctl OSX giving strange results, (continued)

List archive

Re: [perfsonar-user] bwctl OSX giving strange results