Dwarf-2 unwinding vs. manual prologue analysis

[Orjan Friberg]

(Back to gdb-patches@ for patch submission.)

Orjan Friberg wrote:
> 
> Ah, now I see.  The things that broke without any prologue scanning were 
> indeed things like 'next' over library calls (PLT stubs) and things 
> related to call dummys (callfuncs.exp).

Add signal trampolines to that list too.

The change below (committed) doesn't make anything better or worse; it just 
clarifies the situation in which it's assumed that the new CRISv32-specific 
prologue scanner will be used and what conditions are assumed to hold true.

2005-05-27  Orjan Friberg  <orjanf@axis.com>

	* cris-tdep.c (crisv32_scan_prologue): Add.
	(cris_frame_unwind_cache, cris_skip_prologue): Call
	crisv32_scan_prologue when debugging CRISv32.

-- 
Orjan Friberg
Axis Communications

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20050528/12daeef2/attachment.ksh>