[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb-patches
Subject:    [rfc] Extend frame_id_inner by gdbarch parameter
From:       deuling () de ! ibm ! com (Markus Deuling)
Date:       2007-10-31 14:30:00
Message-ID: 47287BD6.208 () de ! ibm ! com
[Download RAW message or body]

Hi,

I'd like to hear your opinion about the attached patch. It gets rid of the last \
remaining occurences of current_gdbarch in frame.c (beside the one in get_frame_arch \
;-) ). Therefor frame_id_inner is extended by a gdbarch parameter. I build and tested \
it on x86 without regression. 

Are there any objections from your side or would this be a way to go? Thanks a lot.

ChangeLog:

	* frame.c (frame_id_inner): Add gdbarch parameter. Replace
	current_gdbarch by gdbarch.
	(frame_find_by_id, get_prev_frame_1): Use get_frame_arch to get at the
	current architecture by frame_info.
	* frame.h (frame_id_inner): Add gdbarch parameter.
	* stack.c (return_command): Use get_frame_arch to get at the current
	architecture by frame_info. Update call of frame_id_inner.
	* infrun.c (handle_inferior_event): Likewise.
	* dummy-frame.c (dummy_frame_push):  Use get_regcache_arch to get at the
	current architecture by regcache. Update call of frame_id_inner.

-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: diff-frame
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20071031/4a3c91f3/attachment.ksh>



[prev in list] [next in list] [prev in thread] [next in thread]