Re: Stack check failure with qemu_x86

Vakul Garg <vakul.garg@...>

I could resolve this issue on qemu_x86 by increasing MAIN_STACK_SIZE in the configuration.

I am not sure whether increasing stack size is required for my hardware board as well or is it only qemu_x86 which exhausted the stack and detected stack overflow.

I am debugging some issue on ARM based board (frdm-k64f) where I suspected corruption.
Does the stack check feature works on arm as well the same way as it worked over qemu_x86?
For the hardware board, zephyr/.config shows HW_STACK_PROTECTION=n.

-----Original Message-----
From: Luiz Augusto von Dentz [mailto:luiz.dentz@...]
Sent: Thursday, December 07, 2017 7:15 PM
To: Vakul Garg <vakul.garg@...>
Cc: zephyr-users@...
Subject: Re: [Zephyr-users] Stack check failure with qemu_x86

Hi Vakul,

On Thu, Dec 7, 2017 at 5:38 AM, Vakul Garg <vakul.garg@...> wrote:

I am running IPSP sample app using qemu_86 (on master branch).

I have enabled following to detect stack corruption.




This results in stack check error.

I tried attaching gdb, but the qemu itself terminates resulting on
closure of debug connection

Can someone give me pointers how to debug the same?

***** Stack Check Fail! *****

Current thread ID = 0x004035a0

Faulting segment:address = 0x0008:0x00003f6f

eax: 0x5be0cd19, ebx: 0xa54ff53a, ecx: 0x6a09e667, edx: 0x3c6ef372

esi: 0x1f83d9ab, edi: 0x510e527f, ebp: 0x9b05688c, esp: 0x0041dff8

eflags: 0x202

Terminate emulator due to fatal kernel error
addr2line -e zephyr/zephyr.elf 0x00003f6f

This is with samples/bluetooth/ipsp sample build with -DBOARD=qemu_x86



Zephyr-users mailing list

Luiz Augusto von Dentz

Join to automatically receive all group messages.