You have to wait first until it crashes and then type bt 
Be careful it barely ever crashes in debug mode, so be prepared for a long run. Use micro USB and connect no sensors
But i typed bt when the firmware crashed. In debug mode happens anyway with our copter.
Read Lander instruction above
Sure, but what i don’t know is how to update the new code!
Look up for “compile from source” page. Switch branch to 3.5rc8. change that line and continue to build the binary.
Than execute the binary instead of the arducopter from debian package
Where can i find that branch? I can’t find it on github. Yeap, i believe that i’m a real newbie with this 
Edit: rc8 is the 3.5 branch?
It’s In the tag. I believe
git checkout Copter3.5.0rc8
Or similar
With 3.5rc8 branch cloned and the line deleted that @lucasdemarchi ask to test, all commands worked fine, unless this one: sudo cp ArduCopter.elf ~/
Then i can’t start apm.service, maybe because of this file.
I was following this: http://ardupilot.org/dev/docs/building-for-erle-brain-2.html
lookat the command window output.
usually its called arducopter, built under build/erlebrain2/bin/arducopter
copy paste this instead
Hi @lucasdemarchi,
The difference between Erle-Brain 2 and Erle-Brain 3 is only the raspberry pi, we’re using Raspberry Pi 3 instead of Raspberry Pi 2.
@ppoirier, you’re running the code on Raspberry Pi Zero, right?
Regards,
Last tests were flawlessly performed on a RPI2 compiled as erlebrain2
Hi @ppoirier,
thanks!
@lucasdemarchi, I run the code with your suggestions:
I’m getting the same error.
What OS are you using @ppoirier?
The problem could be in our OS, the plan for this weekend is create a new one.
Regards,
Latest Raspbian jessie
@josepgomes note that in the screenshot you sent the process received a SIGINT, not a SIGSEGV. Do you have anything else running that can potentially send a SIGINT to the process (other than pressing ctrl-c)…?
1 Like
Oh… No. In that snippet you were running on gdb and pressed ctrl-c. This will interrupt the process at a random point and is not useful for debugging this issue. You need to wait the process to die by itself.
1 Like
Hi @lucasdemarchi,
I’m not so familiar with valgrind, here the output. I’m running properly? Or I need run it with any special flag?
Thanks!!
Regards,
@lucasdemarchi, the problem is in our OS setup, with a vanilla raspbian works without crash.
I’m creating a new release.
Thanks!
Regards,
1 Like
Good !!
So this question was a good one then
1 Like