This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: debug_frame for optimized code
- From: Jim Blandy <jimb at redhat dot com>
- To: Christophe LYON <christophe dot lyon at st dot com>
- Cc: gdb at sourceware dot org
- Date: Wed, 19 Oct 2005 11:37:22 -0700
- Subject: Re: debug_frame for optimized code
- References: <4356312E.70508@st.com>
You should send questions like this to the dwarf-discuss mailing list:
http://mail.freestandards.org/cgi-bin/mailman/listinfo/dwarf-discuss
Christophe LYON <christophe.lyon@st.com> writes:
> Use remember_state after the prologue, and use restore state at LABEL1
> and LABEL2?
> But as states are defined as a stack, it means I would restore twice the
> same thing...
You could save after the prologue, then restore and immediately
re-save at LABEL1, and then restore at LABEL2. But I'm not sure this
strategy generalizes too well.