From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] gdb/dwarf: fix internal error when FDEs do not describe the CFA
Date: Fri, 10 Apr 2026 22:47:00 -0400 [thread overview]
Message-ID: <6f8e8277-c10b-4706-9582-4747d29bb8b5@polymtl.ca> (raw)
In-Reply-To: <87pl4cx8m6.fsf@tromey.com>
On 2026-04-06 14:10, Tom Tromey wrote:
>>>>>> "Simon" == simon marchi <simon.marchi@polymtl.ca> writes:
>
> Simon> The fix consists of handling CFA_UNSET in the dwarf2_frame_cache switch.
> Simon> CFA_UNSET is the initial state when we start interpreting a CFA program,
> Simon> meaning that we don't know yet how the CFA is defined. In our case, it
> Simon> remains unset after interpreting the CFA program.
>
> This makes sense to me, thank you.
> Approved-By: Tom Tromey <tom@tromey.com>
>
> Tom
Thanks, will push both patches.
Simon
next prev parent reply other threads:[~2026-04-11 2:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 17:22 [PATCH 1/2] gdb/testsuite: add .debug_frame support in DWARF assembler Simon Marchi
2026-03-16 17:22 ` [PATCH 2/2] gdb/dwarf: fix internal error when FDEs do not describe the CFA Simon Marchi
2026-03-17 19:33 ` Simon Marchi
2026-03-18 20:27 ` [PATCH v2 1/2] gdb/testsuite: add .debug_frame support in DWARF assembler simon.marchi
2026-03-18 20:27 ` [PATCH v2 2/2] gdb/dwarf: fix internal error when FDEs do not describe the CFA simon.marchi
2026-04-06 18:10 ` Tom Tromey
2026-04-11 2:47 ` Simon Marchi [this message]
2026-04-04 1:25 ` [PATCH v2 1/2] gdb/testsuite: add .debug_frame support in DWARF assembler Simon Marchi
2026-04-06 17:45 ` Tom Tromey
2026-04-11 2:46 ` Simon Marchi
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=6f8e8277-c10b-4706-9582-4747d29bb8b5@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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