CodeChain died with weird syslog while syncing

#### codechain log
```
#910487400 2019-08-29 17:45:23.086394112 block-propagation.ext DEBUG sync Body download completed for #469014(0xdcfa…3e3a)
#910487400 2019-08-29 17:45:23.086455639 Blocks Verifier #1 TRACE headerchain Inserting block header #468079(0x4c3e…bc27) to the headerchain.
#910487400 2019-08-29 17:45:23.086484710 Blocks Verifier #1 TRACE headerchain Block header #468079(0x4c3e…bc27) is already known.
#910487400 2019-08-29 17:45:23.086522552 block-propagation.ext DEBUG sync Body download completed for #469015(0xcbf3…3513)
#910487400 2019-08-29 17:45:23.086582802 Blocks Verifier #1 TRACE blockchain Committing.
#910487400 2019-08-29 17:45:23.086600406 Blocks Verifier #1 TRACE headerchain Committing.
#910487400 2019-08-29 17:45:23.086611712 block-propagation.ext DEBUG sync Body download completed for #469016(0xff03…60fb)
#910487400 2019-08-29 17:45:23.086714764 block-propagation.ext DEBUG sync Body download completed for #469017(0xcb2a…f82c)
#910487400 2019-08-29 17:45:23.089349955 block-propagation.ext DEBUG sync Body download completed for #469018(0x44ef…bd6d)
#910487400 2019-08-29 17:45:23.090128065 block-propagation.ext DEBUG sync Body download completed for #469019(0xc99c…30a3)
#910487400 2019-08-29 17:45:23.091020280 block-propagation.ext DEBUG sync Body download completed for #469020(0xbce3…cb3e)
#910487400 2019-08-29 17:45:23.091109780 block-propagation.ext DEBUG sync Body download completed for #469021(0xde39…5fe2)
#910487400 2019-08-29 17:45:23.091181004 Blocks Verifier #0 TRACE blockchain Inserting block #468080(0x8690…5e97) to the blockchain.
#910487400 2019-08-29 17:45:23.091203175 block-propagation.ext DEBUG sync Body download completed for #469022(0x210c…58b9)
#910487400 2019-08-29 17:45:23.091263216 Blocks Verifier #0 INFO blockchain Block #468080(0x8690…5e97) has higher total score, changing the best proposal/canonical chain.
#910487400 2019-08-29 17:45:23.091298463 block-propagation.ext DEBUG sync Body download completed for #469023(0xb610…8331)
#910487400 2019-08-29 17:45:23.091331039 Blocks Verifier #0 TRACE headerchain Inserting block header #468080(0x8690…5e97) to the headerchain.
#910487400 2019-08-29 17:45:23.091362492 block-propagation.ext DEBUG sync Body download completed for #469024(0x69ed…89f9)
#910487400 2019-08-29 17:45:23.091363794 Blocks Verifier #0 TRACE headerchain Block header #468080(0x8690…5e97) is already known.
#910487400 2019-08-29 17:45:23.091435515 block-propagation.ext DEBUG sync Body download completed for #469025(0x520b…1152)
#910487400 2019-08-29 17:45:23.091496164 Blocks Verifier #0 TRACE blockchain Committing.
#910487400 2019-08-29 17:45:23.091500155 block-propagation.ext DEBUG sync Body download completed for #469026(0x6e9d…199e)
#910487400 2019-08-29 17:45:23.091516882 Blocks Verifier #0 TRACE headerchain Committing.
#910487400 2019-08-29 17:45:23.091599161 block-propagation.ext DEBUG sync Body download completed for #469027(0xb025…73d8)
#910487400 2019-08-29 17:45:23.091655630 block-propagation.ext DEBUG sync Body download completed for #469028(0x6791…f358)
#910487400 2019-08-29 17:45:23.091725194 block-propagation.ext DEBUG sync Body download completed for #469029(0x036d…4b4d)
```

#### syslog
```
Aug 29 17:45:23 tomandjerry-XPS-15-9560 kernel: [112876.566699] traps: Blocks Verifier[1842] trap invalid opcode ip:5641ac1cbc1a sp:7f7d189f0240 error:0 in codechain[5641ab34f000+1276000]
Aug 29 17:45:23 tomandjerry-XPS-15-9560 kernel: [112876.566711] traps: block-propagati[1852] trap invalid opcode ip:5641ac1cbc1a sp:7f7cf0bf61d0 error:0
```

The binary: https://drive.google.com/open?id=1FcZA0ydCemSfNCaS-VMLKkmLMMFPh-oJ
The commithash: c819d743b38ddfc62625e83109ef9c8e0d3b3439
The binary is built from https://github.com/majecty/codechain-1/tree/f/add-sync-log

Start by reproducing the crash during synchronization using the binary built from commit c819d743b38ddfc62625e83109ef9c8e0d3b3439 and compare the CodeChain log with the kernel syslog. Trace the Blocks Verifier and block-propagation processes around the reported invalid opcode; done means identifying the cause and confirming that synchronization no longer terminates those processes.

Written by the indexing model from the issue text.