* [PATCH] Remove function get_frame_memory
@ 2014-01-03 3:12 Yao Qi
0 siblings, 0 replies; only message in thread
From: Yao Qi @ 2014-01-03 3:12 UTC (permalink / raw)
To: gdb-patches
I happen to see that get_frame_memory is not used in gdb or insight. This
patch is to remove it.
gdb:
2014-01-03 Yao Qi <yao@codesourcery.com>
* frame.c (get_frame_memory): Remove.
* frame.h (get_frame_memory): Remove its declaration.
---
gdb/frame.c | 7 -------
gdb/frame.h | 2 --
2 files changed, 0 insertions(+), 9 deletions(-)
diff --git a/gdb/frame.c b/gdb/frame.c
index 10d486c..407de1c 100644
--- a/gdb/frame.c
+++ b/gdb/frame.c
@@ -2403,13 +2403,6 @@ get_frame_address_space (struct frame_info *frame)
/* Memory access methods. */
-void
-get_frame_memory (struct frame_info *this_frame, CORE_ADDR addr,
- gdb_byte *buf, int len)
-{
- read_memory (addr, buf, len);
-}
-
LONGEST
get_frame_memory_signed (struct frame_info *this_frame, CORE_ADDR addr,
int len)
diff --git a/gdb/frame.h b/gdb/frame.h
index f7e46d5..13ad913 100644
--- a/gdb/frame.h
+++ b/gdb/frame.h
@@ -589,8 +589,6 @@ extern void frame_pop (struct frame_info *frame);
If architecture / memory changes are always separated by special
adaptor frames this should be ok. */
-extern void get_frame_memory (struct frame_info *this_frame, CORE_ADDR addr,
- gdb_byte *buf, int len);
extern LONGEST get_frame_memory_signed (struct frame_info *this_frame,
CORE_ADDR memaddr, int len);
extern ULONGEST get_frame_memory_unsigned (struct frame_info *this_frame,
--
1.7.7.6
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-01-03 3:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-03 3:12 [PATCH] Remove function get_frame_memory Yao Qi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).