> There is a problem though (and I only noticed after committing it :-().
> 
> The change assumes that all architectures that use generic dummy frames also set PC_IN_CALL_DUMMY to generic_pc_in_call_dummy() (and hence eventually call this new pc_in_dummy_frame).  Problem is, some don't:
>     cris, frv, i386, x86-64
> They instead use pc_in_call_dummy_at_entry_point().  Now, in theory, generic_pc_in_call_dummy() and pc_in_call_dummy_at_entry_point() are equivalent, I'm not going to put money on it though.  Hence, expect a follow up patch to revert a small part of this change.

I've checked in the attached.

Andrew