From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>
Subject: [PATCH 3/3] Remove set_breakpoint_data definition in GDBServer.
Date: Fri, 23 Oct 2015 17:09:00 -0000 [thread overview]
Message-ID: <1445543917-16839-4-git-send-email-antoine.tremblay@ericsson.com> (raw)
In-Reply-To: <1445543917-16839-1-git-send-email-antoine.tremblay@ericsson.com>
This patch removes the now unused set_breakpoint_data function from mem_break.h
gdb/gdbserver/ChangeLog:
* mem-break.h (set_breakpoint_data): Remove.
---
gdb/gdbserver/mem-break.h | 5 -----
1 file changed, 5 deletions(-)
diff --git a/gdb/gdbserver/mem-break.h b/gdb/gdbserver/mem-break.h
index fa9d300..d199cc4 100644
--- a/gdb/gdbserver/mem-break.h
+++ b/gdb/gdbserver/mem-break.h
@@ -194,11 +194,6 @@ void check_mem_read (CORE_ADDR mem_addr, unsigned char *buf, int mem_len);
void check_mem_write (CORE_ADDR mem_addr,
unsigned char *buf, const unsigned char *myaddr, int mem_len);
-/* Set the byte pattern to insert for memory breakpoints. This function
- must be called before any breakpoints are set. */
-
-void set_breakpoint_data (const unsigned char *bp_data, int bp_len);
-
/* Delete all breakpoints. */
void delete_all_breakpoints (void);
--
1.9.1
next prev parent reply other threads:[~2015-10-22 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 16:50 [PATCH 0/3] Fix nto, spu and win32 builds of GDBServer Antoine Tremblay
2015-10-23 17:02 ` [PATCH 2/3] Fix nto,spu " Antoine Tremblay
2015-10-23 17:09 ` Antoine Tremblay [this message]
2015-10-23 17:23 ` [PATCH 1/3] Refactor default_breakpoint_kind_from_pc to be used by all targets in GDBServer Antoine Tremblay
2015-10-23 23:56 ` [PATCH 0/3] Fix nto, spu and win32 builds of GDBServer Pedro Alves
2015-10-25 2:31 ` Antoine Tremblay
2015-10-25 11:08 ` Aleksandar Ristovski
2015-10-25 2:42 ` Aleksandar Ristovski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1445543917-16839-4-git-send-email-antoine.tremblay@ericsson.com \
--to=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox