2010/5/28 Brendan Tauras
> I am writing an asynchronous polling application and testing it for
> memory leaks with valgrind. I got valgrind errors regarding system
> call parameters pointing to uninitiailzed data on the stack (but the
> program runs as expected).
>
> Then I ran the simple asynch
I am writing an asynchronous polling application and testing it for
memory leaks with valgrind. I got valgrind errors regarding system
call parameters pointing to uninitiailzed data on the stack (but the
program runs as expected).
Then I ran the simple asynchronous application tutorial code (
htt
On Fri, May 28, 2010 at 5:47 PM, Leonardo Chiquitto <
leonardo.li...@gmail.com> wrote:
> On Fri, May 28, 2010 at 12:33 PM, Bart Van Assche
> wrote:
> > On Fri, May 28, 2010 at 3:30 PM, Leonardo Chiquitto
> > wrote:
> >>
> >> Some weeks ago, our build checks started to complain about "portability
On Fri, May 28, 2010 at 12:33 PM, Bart Van Assche wrote:
> On Fri, May 28, 2010 at 3:30 PM, Leonardo Chiquitto
> wrote:
>>
>> Some weeks ago, our build checks started to complain about "portability
>> issues"
>> when building net-snmp from trunk:
>>
>> E: net-snmp 64bit-portability-issue host/hr
On Fri, May 28, 2010 at 3:30 PM, Leonardo Chiquitto <
leonardo.li...@gmail.com> wrote:
> Some weeks ago, our build checks started to complain about "portability
> issues"
> when building net-snmp from trunk:
>
> E: net-snmp 64bit-portability-issue host/hr_swinst.c:573, 574, 679, 681
>
Which arg
On Fri, May 28, 2010 at 3:30 PM, Leonardo Chiquitto <
leonardo.li...@gmail.com> wrote:
> Some weeks ago, our build checks started to complain about "portability
> issues"
> when building net-snmp from trunk:
>
> E: net-snmp 64bit-portability-issue host/hr_swinst.c:573, 574, 679, 681
>
> Here's th
