Restarted test node from wedged state @ +/- few seconds Thu Feb 27 14:14:10 CDT 2020

Catching up to max height... 619269

SetBestChain: new best=000000000000000000027e3d7e3ec95cd069e7564d804c9a1e5cfb31476c0b07  height=619269  work=4051295203667456755228954486

Complete.

Now to let the node get 10 connections, currenly has 6...

Done, now has 10 connections.

--------------------------------------------------------------------------

Code changes:  None.  Stock TRB. 

Running as:  valgrind -v --tool=massif --massif-out-file=massif.bitcoind.test7.log ./bitcoind 

--------------------------------------------------------------------------

Test 7:  Send 49999 'getdata for block' commands to the node, see how it reacts and if
it recovers.  Host, Port, File = 127.0.0.1, 8333, snap_49999.txt  Collect vmstat before, during, and after.
Also collect a valgrind of the heap usage with massif output (_WITHOUT_ --pages-as-heap flag).

mod6@localhost ~ $ ./wedger.py 127.0.0.1 8333 snap_49999.txt 
<INCOMING MESSAGE: 'version', 115 bytes>
Alive: V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=1.2.3.4:8333 Blocks=619271
<INCOMING MESSAGE: 'verack', 0 bytes>
Sending 1799991-byte message packet...
Now listening for replies (Ctl-C to quit...)
<INCOMING MESSAGE: 'getblocks', 1029 bytes>
<INCOMING MESSAGE: 'block', 978262 bytes>
<INCOMING MESSAGE: 'block', 974661 bytes>
<INCOMING MESSAGE: 'block', 968422 bytes>
<INCOMING MESSAGE: 'block', 967259 bytes>
<INCOMING MESSAGE: 'block', 972178 bytes>
<INCOMING MESSAGE: 'block', 985159 bytes>
<INCOMING MESSAGE: 'block', 975364 bytes>
<INCOMING MESSAGE: 'block', 971491 bytes>
<INCOMING MESSAGE: 'block', 980567 bytes>
<INCOMING MESSAGE: 'block', 971218 bytes>
<INCOMING MESSAGE: 'block', 980230 bytes>
<INCOMING MESSAGE: 'block', 940125 bytes>
<INCOMING MESSAGE: 'block', 980598 bytes>
<INCOMING MESSAGE: 'block', 250 bytes>
<INCOMING MESSAGE: 'block', 985780 bytes>
<INCOMING MESSAGE: 'block', 983458 bytes>
<INCOMING MESSAGE: 'block', 983389 bytes>
<INCOMING MESSAGE: 'block', 980792 bytes>
<INCOMING MESSAGE: 'block', 961972 bytes>
<INCOMING MESSAGE: 'block', 981154 bytes>
<INCOMING MESSAGE: 'block', 984256 bytes>
<INCOMING MESSAGE: 'block', 988202 bytes>
<INCOMING MESSAGE: 'block', 988155 bytes>
<INCOMING MESSAGE: 'block', 989400 bytes>
<INCOMING MESSAGE: 'block', 974575 bytes>
<INCOMING MESSAGE: 'block', 984036 bytes>
Violated BTC Protocol: Invalid payload length!


....

In the debug.log after all of the request spam:

Ate 49,999 of these:

received getdata for: block 00000000000000000048bd41931f1ee411eac82a5073afc1f3693719655a69cf
received getdata for: block 00000000000000000012c785558fb1b84d1c48a50b20567f9000f8fef8a26468

Wedged.

Not responding to RPC commands.

Valgrind is not outputting its logged information from the test -- bitcoind is wedged and 
neither `kill -TERM` `kill -SIGTERM`, nor `kill` will cause it to hangup gracefully and
report it's collections from the test.  A `kill -9` will not do this successfully either.
Very likely not going to work as this bin is musl & static; valgrind is only for libc, not
musl nor static.

-----------------------------------------------------------------------
Debugging section:

--------------------------------------------------------------------------