[commit] Was: [rfc] unwind_dummy_id

[Andrew Cagney]

> http://sources.redhat.com/ml/gdb/2003-02/msg00549.html
> 
> This patch adds such a mechanism.  I'm going to table this until someone comes up with evidence that it actually fixes a bug :-)

I've found my evidence.  The d10v's stack pointer and frame base sit at 
oposite ends of a d10v frame.  Consequently, when unwinding interleaved 
  frameless functions and dummy frames, the dummy-frame code can 
mis-locate a dummy frame (one dummy's sp matches the other dummy's fp). 
  Using save_dummy_frame_tos() and unwind_dummy_id() ensures that each 
dummy frame is identified by a single unique value.

> > Anyway. Eli, does the doco look ok?
> Yes, thanks.

I've commited the attached.  It's been updated to work with current 
sources.  It also gained a few more comments and, when the new code, an 
extra sanity check.

Andrew

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: diffs
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20030305/366a8bdc/attachment.ksh>