[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libunwind] unwinding through dynamically modified code?

From: Todd L Miller
Subject: Re: [libunwind] unwinding through dynamically modified code?
Date: Thu, 25 Mar 2004 17:34:30 -0600 (CST)

> Isn't that what it is?  It's just a sequential numbering of _all_ the
> IA-64 instructions in the region (while ignoring the fact that MLX
> bundles really have only 2, not 3 instructions).

        It must not have been clear from the fragment, but
unwindRegion->insn_count is incremented appropriately as I generate the
code fragment.  (Our two methods always return the same index.)

> The "gp" member in the "unw_dyn_info_t" structure needs to be set to
> the value that the GP should have in your procedure.

        OK.  Simple enough. :)

> No, copy_state/label_state only work within a procedure.  The unwinder
> simply processes them in linear order when parsing the descriptors for
> a procedure.  It doesn't retain any info about _other_ procedures.

        So the correct thing to do in this circumstance is to try the
refinement you just suggested?

- Todd Miller

reply via email to

[Prev in Thread] Current Thread [Next in Thread]