libbacktrace fails to capture async exceptions

[arnetheduck]

make USE_LIBBACKTRACE=0 witti

DBG 2020-06-04 09:40:53+02:00 Could not write to connection              tid=22026 file=secio.nim:247 msg="Write couldn\'t finish writing\nAsync traceback:\n  /home/arnetheduck/status/nim-beacon-chain/vendor/nim-testutils/testutils/moduletests.nim(21)              beacon_node\n  /home/arnetheduck/status/nim-beacon-chain/beacon_chain/beacon_node.nim(991)                               main\n  /home/arnetheduck/status/nim-beacon-chain/beacon_chain/beacon_node.nim(763)                               start\n  /home/arnetheduck/status/nim-beacon-chain/beacon_chain/beacon_node.nim(716)                               run\n  /home/arnetheduck/status/nim-beacon-chain/vendor/nim-chronos/chronos/asyncloop.nim(278)                   poll\n  /home/arnetheduck/status/nim-beacon-chain/vendor/nim-libp2p/libp2p/stream/chronosstream.nim(65)           write\n  #[\n    /home/arnetheduck/status/nim-beacon-chain/vendor/nim-testutils/testutils/moduletests.nim(21)              beacon_node\n    /home/arnetheduck/status/nim-beacon-chain/beacon_chain/beacon_node.nim(991)                               main\n    /home/arnetheduck/status/nim-beacon-chain/beacon_chain/beacon_node.nim(763)                               start\n    /home/arnetheduck/status/nim-beacon-chain/beacon_chain/beacon_node.nim(716)                               run\n    /home/arnetheduck/status/nim-beacon-chain/vendor/nim-chronos/chronos/asyncloop.nim(278)                   poll\n    /home/arnetheduck/status/nim-beacon-chain/vendor/nimbus-build-system/vendor/Nim/lib/system/excpt.nim(126) write\n  ]#\nException message: Write couldn\'t finish writing\nException type:" topic=secio

make witti

DBG 2020-06-04 08:54:11+02:00 Could not write to connection              tid=12715 file=secio.nim:247 msg="Write couldn\'t finish writing\nAsync traceback:\nException message: Write couldn\'t finish writing\nException type:" topic=secio

These two log lines show how enabling libbacktrace disables collection of stack traces for async.

A separate issue is that async stack traces should absolutely not be put in the msg field: status-im/nim-chronos#100

bcbfa73

[stefantalpalaru]

USE_LIBBACKTRACE=1

You mean 0? 1 is the default.

[arnetheduck]

right, =0