This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: unwind_pc

From: Andrew Cagney <cagney at gnu dot org>
To: "Vineet Sharma, Noida" <vineets at noida dot hcltech dot com>
Cc: gdb at sources dot redhat dot com
Date: Mon, 23 Feb 2004 10:51:47 -0500
Subject: Re: unwind_pc
References: <1B3885BC15C7024C845AAC78314766C503929120@exch-01.noida.hcltech.com>

Hi All,
		Whats the main purpose of the unwind_pc() ? What is it
supposed to do?. which target doesnt need it and why?


@item CORE_ADDR unwind_pc (struct frame_info *@var{this_frame})
@findex unwind_pc
@anchor{unwind_pc} Return the instruction address, in @var{this_frame}'s
caller, at which execution will resume after @var{this_frame} returns.
This is commonly refered to as the return address.

The implementation, which must be frame agnostic (work with any frame),
is typically no more than:

@smallexample
ULONGEST pc;
frame_unwind_unsigned_register (this_frame, D10V_PC_REGNUM, &pc);
return d10v_make_iaddr (pc);
@end smallexample

Andrew

References:
- unwind_pc
  - From: Vineet Sharma, Noida

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]