From: jh--- via Gdb <gdb@sourceware.org>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: gdb@sourceware.org
Subject: Re: Creating and using dwarf information for ARMv7-A exception handlers
Date: Thu, 27 Nov 2025 09:13:47 +0100 [thread overview]
Message-ID: <3b2d8fa20308547f303e0ad605ac3a29@clesse.com> (raw)
In-Reply-To: <cfaf019f7a3a54cd896c55e4db46eeaa97a8772d.camel@starynkevitch.net>
Le 2025-11-26 11:05, Basile Starynkevitch a écrit :
> On Wed, 2025-11-26 at 11:00 +0100, jh--- via Gdb wrote:
>> Hi,
>>
>> I am working on an embedded target with a Cortex-A9 CPU. There is a
>> debug tool based on Eclipse and gdb 10.2.
>> I would like (if it is possible) to have a complete stack trace when
>> my
>> code is in the SVC handler.
>
>
> Did you consider using (in your code, not in GDB)
> https://github.com/ianlancetaylor/libbacktrace
Hi,
Thank you for you answer.
Is gdb using libbacktrace to perform the call stack unwind?
Best regards,
JH.
next prev parent reply other threads:[~2025-11-27 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1916c229fb1f148902bf15a1b60dedbe@clesse.com>
[not found] ` <51ebaf670472865c9abb31854e16c795@clesse.com>
2025-11-26 10:00 ` jh--- via Gdb
2025-11-26 10:05 ` Basile Starynkevitch
2025-11-27 8:13 ` jh--- via Gdb [this message]
2025-11-27 8:41 ` Basile Starynkevitch
2025-12-01 19:59 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b2d8fa20308547f303e0ad605ac3a29@clesse.com \
--to=gdb@sourceware.org \
--cc=basile@starynkevitch.net \
--cc=jh@clesse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox