Backtraces with interrupts or signals seem unreliable, anyone else seen this?

[Keith Owens]

On Tue, 10 Jun 2003 16:08:13 -0700, 
Steven Dake <sdake at mvista.com> wrote:
>It seems when an interrupt or signal occurs, which results in an 
>exception frame (with frame pointers on), KDB has trouble decoding that 
>frame properly when using the backtrace functionality.  If I get past 
>the exception frame, the rest of the backtrace looks fine.
>
>Has anyone seen this behavior?  I am using KDB 4.1. 

Which architecture?  Every arch has different ways of decoding the
frames.