Re: [Bitcoin-development] Another uninitialized memory problem

2014-06-03 Thread Jeff Garzik
Does this fix it? https://github.com/bitcoin/bitcoin/pull/4282 On Tue, Jun 3, 2014 at 12:47 PM, Toshi Morita wrote: > I looked at this a bit more yesterday, and it looks like both sides of the > comparison were uninitialized, and I fixed one side, but the other side has > the same problem. > >

Re: [Bitcoin-development] Another uninitialized memory problem

2014-06-03 Thread Toshi Morita
I looked at this a bit more yesterday, and it looks like both sides of the comparison were uninitialized, and I fixed one side, but the other side has the same problem. I'll try to investigate further this afternoon once I get out of meetings/meetings prep. Toshi On Tue, Jun 3, 2014 at 9:43 AM

Re: [Bitcoin-development] Another uninitialized memory problem

2014-06-03 Thread Jeff Garzik
I think I see the problem. On Mon, Jun 2, 2014 at 4:01 PM, Toshi Morita wrote: > I'm seeing another uninitialized memory problem in bitcoind using valgrind: > > tm@tm-VirtualBox:~/bitcoind/bitcoin/src$ valgrind ./bitcoind > ==2337== Memcheck, a memory error detector > ==2337== Copyright (C) 2002

Re: [Bitcoin-development] Another uninitialized memory problem

2014-06-03 Thread Wladimir
On Mon, Jun 2, 2014 at 10:01 PM, Toshi Morita wrote: > I'm seeing another uninitialized memory problem in bitcoind using valgrind: Thanks for the report. Which version/commit id of bitcoind? Wladimir -- Learn Graph Dat