Backtrace stopped: previous frame identical to this frame (corrupt stack?)

RE: Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Wiktor — Wed, 21 May 2014 10:05:51 GMT

Ofcourse it is not big problem but sometimes annoying :) I will try to get help from nordic support, and if they give me any solution I'll post here. Thank you for your response.

RE: Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Eliot Stock — Wed, 21 May 2014 09:50:43 GMT

I'm not sure how much debugging you can do while the radio's in use at all, whether connected or advertising. Possibly very little. There's no source for the Soft Device code so gdb gets confused. I never really got to the bottom of it and settled for working around it.

RE: Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Wiktor — Wed, 21 May 2014 09:43:53 GMT

Yes, but it will happenes even if i'm connected.

RE: Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Eliot Stock — Wed, 21 May 2014 09:32:53 GMT

So are you advertising while trying to debug then?

RE: Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Wiktor — Wed, 21 May 2014 09:30:50 GMT

Hi Eliot,

I have a same problem. I notice that when I step over or set breakpoint at any stack function call, the program will end in 0x2000000a adress. Have You solve this issue?

Regards

RE: Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Eliot Stock — Mon, 07 Apr 2014 18:40:13 GMT

Got it: the difference between when I was last able to do this and now is that I'm now advertising while trying to debug.

Can I not do that at all? What about if I'm not advertising but I'm connected, so I'm using the radio occasionally?