jacobrosenthal commented on issue #801: Split status: non-matching (1) when 
(near?) out of memory
URL: https://github.com/apache/mynewt-core/issues/801#issuecomment-364498830
 
 
   No idea. All I know is what I posted above, so in future if anyone is
   seeing non-matching (1), it might be a memory issue, stack or otherwise. I
   Don't really care if this is marked wont fix, just wanted to document it as
   Ive been randomly seeing it over the last month and couldnt figure out if
   it was a specific target or newt or newtmgr bug, and now I believe it has
   something to do with newt-core and low memory.
   
   On Fri, Feb 9, 2018 at 9:10 AM, ccollins476ad <notificati...@github.com>
   wrote:
   
   > By "memory", do you mean stack size? A stack overflow will yield
   > unpredictable behavior, and I'm afraid not much can be done about that.
   >
   > ?
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/mynewt-core/issues/801#issuecomment-364478275>,
   > or mute the thread
   > 
<https://github.com/notifications/unsubscribe-auth/AAb0dGNgemsKsGejLNUhcettpz8ZhXH4ks5tTG4DgaJpZM4R_avN>
   > .
   >
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to