Just general comments, I hope I’m not saying things which are too obvious. Either g_os_run_list or one of the task structures is getting smashed. As you know you tasks beforehand, you can walk through them manually to figure which one it is.
Usually culprit is stack overflow, so once you find out which task structure is being corrupt, look for the stack just after that in memory. nm output piped to sort is your friend in locating that stack. Hope this helps, M > On Apr 19, 2017, at 11:08 AM, Jacob Rosenthal <[email protected]> wrote: > > Anyone have thoughts on debugging the scheduler crash? That point gets hit > constantly, so breaking there is tough, break commands and logging also > appears to mess with bluetooth timing as I cant get a connect when I do > that. > > On Mon, Apr 17, 2017 at 10:49 AM, Jacob Rosenthal <[email protected]> > wrote: > >> b * 0x00008eda
