[
https://issues.apache.org/jira/browse/MYNEWT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731426#comment-15731426
]
ASF subversion and git services commented on MYNEWT-245:
--------------------------------------------------------
Commit f433a77ef2819ed1848215312a88a1ad20a69013 in incubator-mynewt-core's
branch refs/heads/develop from [~ccollins476]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=f433a77
]
MYNEWT-245 Allow debug of unittest via "newt run"
This change is required to enable the sibling change to work to function
properly. With both changes, a unittest package can be debugged via:
newt run <unittest-pkg>
This builds the test executable such that a failed test triggers a
failed assert and runs it in gdb. When a test fails, gdb halts at the
point of failure.
> newt target test should allow debug of a package test library
> -------------------------------------------------------------
>
> Key: MYNEWT-245
> URL: https://issues.apache.org/jira/browse/MYNEWT-245
> Project: Mynewt
> Issue Type: Improvement
> Components: Newt
> Reporter: Paul Dietrich
> Assignee: Christopher Collins
> Fix For: v1_0_0_rel
>
>
> when I hit an assert in my test, I wanted to debug to see why it was
> asserting. It turns out that there was no way to do that in newt.
> It would be nice to have this capability.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
