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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MYNEWT-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325379#comment-15325379 ] 

ASF subversion and git services commented on MYNEWT-304:
--------------------------------------------------------

Commit 6ed23d287cc31e46b6fb9aff1062a68ad51889bd in incubator-mynewt-core's branch refs/heads/develop from [~marko]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6ed23d2 ]

MYNEWT-304; mcu hal - add routine system_debugger_attached() which tells
whether debugging via JTAG or not. If yes, we can stop in debugger
when system crashes/resets.


> 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
>            Reporter: Marko Kiiskila
>            Assignee: Marko Kiiskila
>
> 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)