Closed microbuilder closed 8 years ago
Not related to this issue, but I added some notes in the documentation folder on debugging these crash dumps to trace it back to the offending line of code via gdb
or objdump
: https://github.com/adafruit/Adafruit_Mynewt/blob/master/docs/14_FieldDebugging.md
Nah, it is the help instruction for using nustest that I print out upon reset to remind us how to run this command https://github.com/adafruit/Adafruit_Mynewt/blob/master/apps/throughput/src/main.c#L338
nustest <count> <packetsize>
Ah I didn't see that ... I think there shouldn't be printf like that unless we run the command or ask for the help params. Can you comment that out? Glad it's not a bug though, I wasn't sure what was happening to make that command fire and worried it was something more complicated. :)
To do some pre-release tests I enabled the
crash_test
library in the throughput app, just to make sure tasks can die properly and to test out some of the logging and debugging tools.Building the throughput example you can run the
crash
command from the shell with a specific error likecrash div0
orcrash jump0
.The tasks fail gracefully, but every time an error occurs
nustest
is being executed unexpectedly, which shouldn't be happening: