[jira] [Resolved] (MYNEWT-304) assert() drops into debugger in the wrong place

["Marko Kiiskila (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MYNEWT-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marko Kiiskila resolved MYNEWT-304.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: v0_10_0

Added MCU specific routine which tells whether JTAG adapter is attached or not. Use this from __assert_func() to figure out whether to drop into debugger or not.

> assert() drops into debugger in the wrong place
> -----------------------------------------------
>
>                 Key: MYNEWT-304
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-304
>             Project: Mynewt
>          Issue Type: Bug
>    Affects Versions: v0_10_0
>            Reporter: Marko Kiiskila
>            Assignee: Marko Kiiskila
>             Fix For: v0_10_0
>
>
> It used to be that on assert() the debugger would leave in a state where you could do backtrace from debugger. Now, in order to get coredump, we fault before we check to whether we should drop into debugger.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)