public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
* [Bug tdep/28829] New: ARM Cortex-M: cannot backtrace from interrupt handler
@ 2022-01-27 13:11 clyon at gcc dot gnu.org
2022-05-09 6:55 ` [Bug tdep/28829] " clyon at gcc dot gnu.org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: clyon at gcc dot gnu.org @ 2022-01-27 13:11 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=28829
Bug ID: 28829
Summary: ARM Cortex-M: cannot backtrace from interrupt handler
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Hello,
Playing with sample STM32 code on a board with Cortex-M33 and Security
extension (STM32L552) I put a breakpoint in SysTick_Handler
from
NUCLEO-L552ZE-Q/Examples/GTZC/GTZC_TZSC_MPCBB_TrustZone/NonSecure/Src/stm32l5xx_it.c:132
When I ask for a backtrace, with GDB trunk I get:
(gdb) bt
#0 SysTick_Handler ()
at [...]/stm32l5xx_it.c:132
Backtrace stopped: Cannot access memory at address 0xd034f8d6
If I apply the patches I posted recently to add support for FNC_RETURN on such
devices
(https://sourceware.org/pipermail/gdb-patches/2022-January/185127.html), I get:
(gdb) bt
#0 SysTick_Handler ()
at [...]/stm32l5xx_it.c:132
#1 <signal handler called>
#2 0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
which only partially better ;-)
When I single-step in gdb's arm_m_exception_cache, I notice that
sp = get_frame_register_unsigned (this_frame, ARM_SP_REGNUM);
returns 0x2002ff78, but later in the same function
unwound_sp = arm_cache_get_prev_sp (cache, tdep);
returns 0x2002ff70.
Since the breakpoint is set after the prologue, I think I might need to add
something like
arm_scan_prologue (this_frame, cache);
but this leads to a crash.
Looking into arm_scan_prologue, I was surprised to see that arm_frame_is_thumb
returns false although the processor is Cortex-M (so thumb-only).
This is because t_bit == 0x1000000 and cpsr == 0xf, which is surprising?
I have access to the board only until tomorrow, so I'm dumping my findings here
in case I can get help very quickly or someone else picks up the problem later.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug tdep/28829] ARM Cortex-M: cannot backtrace from interrupt handler 2022-01-27 13:11 [Bug tdep/28829] New: ARM Cortex-M: cannot backtrace from interrupt handler clyon at gcc dot gnu.org @ 2022-05-09 6:55 ` clyon at gcc dot gnu.org 2022-10-21 10:03 ` luis.machado at arm dot com ` (3 subsequent siblings) 4 siblings, 0 replies; 6+ messages in thread From: clyon at gcc dot gnu.org @ 2022-05-09 6:55 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=28829 Christophe Lyon <clyon at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug tdep/28829] ARM Cortex-M: cannot backtrace from interrupt handler 2022-01-27 13:11 [Bug tdep/28829] New: ARM Cortex-M: cannot backtrace from interrupt handler clyon at gcc dot gnu.org 2022-05-09 6:55 ` [Bug tdep/28829] " clyon at gcc dot gnu.org @ 2022-10-21 10:03 ` luis.machado at arm dot com 2022-10-21 10:08 ` clyon at gcc dot gnu.org ` (2 subsequent siblings) 4 siblings, 0 replies; 6+ messages in thread From: luis.machado at arm dot com @ 2022-10-21 10:03 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=28829 Luis Machado <luis.machado at arm dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING CC| |luis.machado at arm dot com --- Comment #1 from Luis Machado <luis.machado at arm dot com> --- Hi Christophe. Has this been addressed? -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug tdep/28829] ARM Cortex-M: cannot backtrace from interrupt handler 2022-01-27 13:11 [Bug tdep/28829] New: ARM Cortex-M: cannot backtrace from interrupt handler clyon at gcc dot gnu.org 2022-05-09 6:55 ` [Bug tdep/28829] " clyon at gcc dot gnu.org 2022-10-21 10:03 ` luis.machado at arm dot com @ 2022-10-21 10:08 ` clyon at gcc dot gnu.org 2022-10-21 12:05 ` torbjorn.svensson at st dot com 2022-10-21 12:10 ` luis.machado at arm dot com 4 siblings, 0 replies; 6+ messages in thread From: clyon at gcc dot gnu.org @ 2022-10-21 10:08 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=28829 Christophe Lyon <clyon at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |torbjorn.svensson at st dot com --- Comment #2 from Christophe Lyon <clyon at gcc dot gnu.org> --- Yes I think that was fixed earlier this year. I think Torbjörn can confirm. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug tdep/28829] ARM Cortex-M: cannot backtrace from interrupt handler 2022-01-27 13:11 [Bug tdep/28829] New: ARM Cortex-M: cannot backtrace from interrupt handler clyon at gcc dot gnu.org ` (2 preceding siblings ...) 2022-10-21 10:08 ` clyon at gcc dot gnu.org @ 2022-10-21 12:05 ` torbjorn.svensson at st dot com 2022-10-21 12:10 ` luis.machado at arm dot com 4 siblings, 0 replies; 6+ messages in thread From: torbjorn.svensson at st dot com @ 2022-10-21 12:05 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=28829 --- Comment #3 from Torbjörn SVENSSON <torbjorn.svensson at st dot com> --- (In reply to Christophe Lyon from comment #2) > Yes I think that was fixed earlier this year. I think Torbjörn can confirm. I think that this issue has been resolved, but I don't remember to has seen it myself. Maybe we can resolve it and if we see something similar in the future, we can address it then? -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug tdep/28829] ARM Cortex-M: cannot backtrace from interrupt handler 2022-01-27 13:11 [Bug tdep/28829] New: ARM Cortex-M: cannot backtrace from interrupt handler clyon at gcc dot gnu.org ` (3 preceding siblings ...) 2022-10-21 12:05 ` torbjorn.svensson at st dot com @ 2022-10-21 12:10 ` luis.machado at arm dot com 4 siblings, 0 replies; 6+ messages in thread From: luis.machado at arm dot com @ 2022-10-21 12:10 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=28829 Luis Machado <luis.machado at arm dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #4 from Luis Machado <luis.machado at arm dot com> --- Sounds good. Please reopen if needed. Thanks! -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-10-21 12:10 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-01-27 13:11 [Bug tdep/28829] New: ARM Cortex-M: cannot backtrace from interrupt handler clyon at gcc dot gnu.org 2022-05-09 6:55 ` [Bug tdep/28829] " clyon at gcc dot gnu.org 2022-10-21 10:03 ` luis.machado at arm dot com 2022-10-21 10:08 ` clyon at gcc dot gnu.org 2022-10-21 12:05 ` torbjorn.svensson at st dot com 2022-10-21 12:10 ` luis.machado at arm dot com
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).