[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: |
Tue, 23 Mar 2004 23:48:03 -0600 (CST) |
> UNW_IA64_SP is what you want to use. UNW_IA64_GR+12 only tells you
> about the last time the stack-pointer was saved, which is hardly
> useful.
I'm not quite sure I understand the difference. I'm away from my
references right now, but isn't the stack pointer defined to be r12? (At
least, during normal operation, but that's precisely what I'm supposed to
be describing with the unwind information, right?) Or is this distinction
more for the benefit of libunwind?
- Todd Miller
- Re: [libunwind] unwinding through dynamically modified code?, (continued)
- Re: [libunwind] unwinding through dynamically modified code?, David Mosberger, 2004/03/26
- [libunwind] multiple dynamic list-info addresses?, Todd L Miller, 2004/03/29
- [libunwind] Re: multiple dynamic list-info addresses?, David Mosberger, 2004/03/29
- [libunwind] Re: multiple dynamic list-info addresses?, Todd L Miller, 2004/03/30
- [libunwind] Re: multiple dynamic list-info addresses?, David Mosberger, 2004/03/30
- [libunwind] Re: multiple dynamic list-info addresses?, Todd L Miller, 2004/03/31
- [libunwind] Re: multiple dynamic list-info addresses?, David Mosberger, 2004/03/31
- [libunwind] Re: multiple dynamic list-info addresses?, Todd L Miller, 2004/03/31
Re: [libunwind] unwinding through dynamically modified code?, Todd L Miller, 2004/03/23
Message not availableMessage not availableRe: [libunwind] unwinding through dynamically modified code?, Todd L Miller, 2004/03/24