This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: What should be used instead of deprecated_read_memory_nobpt()?
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: pgilliam at us dot ibm dot com
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 29 Nov 2005 23:04:27 +0100 (CET)
- Subject: Re: What should be used instead of deprecated_read_memory_nobpt()?
- References: <200511291401.30945.pgilliam@us.ibm.com>
> From: Paul Gilliam <pgilliam@us.ibm.com>
> Date: Tue, 29 Nov 2005 14:01:30 -0800
>
> I need to write an implementation of
> 'gdbarch_in_function_epilogue_p()'. In looking for a model to use,
> I see that 'hppa_in_function_epilogue_p()' and
> 's390_in_function_epilogue_p()' both use
> 'deprecated_read_memory_nobpt()' to get instructions from the
> target, but 'sh_in_function_epilogue_p()' and
> 'xstormy16_in_function_epilogue_p()' both use
> 'read_memory_unsigned_integer()' for that purpose.
>
> Can 'read_memory_unsigned_integer()' replace 'deprecated_read_memory_nobpt()'?
Not sure, but read_memory_unsigned_integer() might not be safe,
because of the possibility of inserted breakpoints. The safe
alternative is safe_frame_unwind_memory(). But of course that means
that in_function_epilogue_p should really be changed such that it
accepts a `struct frame *' as an argument.
Mark