[
https://issues.apache.org/jira/browse/MYNEWT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860107#comment-15860107
]
ASF subversion and git services commented on MYNEWT-624:
--------------------------------------------------------
Commit 859540e3440601c0c1808f6b40a923bbda7a52c6 in incubator-mynewt-core's
branch refs/heads/develop from [~vrahane]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=859540e
]
MYNEWT-624 apps/slinky: Syscfg sets wrong config
- Fixing builds which use split images. The loader app should not be
specifying the OS_MAIN_STACK_SIZE because the second app is specifying
it.
- The way this would affect unified images is: It would use the default
Os_MAIN_STACK_SIZE set in the OS which is 1024.
> apps/slinky: Syscfg sets wrong config setting OS_MAIN_STACKS_SIZE
> -----------------------------------------------------------------
>
> Key: MYNEWT-624
> URL: https://issues.apache.org/jira/browse/MYNEWT-624
> Project: Mynewt
> Issue Type: Bug
> Affects Versions: v1_0_0_beta2
> Reporter: Vipul Rahane
> Assignee: Vipul Rahane
> Labels: apps
> Fix For: v1_0_0_rel
>
>
> Syscfg sets wrong config setting OS_MAIN_STACKS_SIZE, it should be
> OS_MAIN_STACK_SIZE.
> There was more than one problem here:
> 1. OS_MAIN_STACKS_SIZE should have been OS_MAIN_STACK_SIZE.
> 2. For images being built as split images, the loader and the app need to
> have the same OS_MAIN_STACK_SIZE.
> Solution:
> Remove OS_MAIN_STACK_SIZE from slinky/syscfg.yml so that it uses
> OS_MAIN_STACK_SIZE from the second app and not the loader.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
