public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Remove bkpt_base_breakpoint_ops Date: Fri, 29 Apr 2022 22:24:01 +0000 (GMT) [thread overview] Message-ID: <20220429222401.5C2763858434@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=823b50f3857846fe7cd8fb8831a13797903885b8 commit 823b50f3857846fe7cd8fb8831a13797903885b8 Author: Tom Tromey <tom@tromey.com> Date: Sun Jan 16 09:00:21 2022 -0700 Remove bkpt_base_breakpoint_ops An earlier patch removed the last use of bkpt_base_breakpoint_ops, so remove the object entirely. Diff: --- gdb/breakpoint.c | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index 2c0a2aac191..67b9313ad83 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -229,11 +229,6 @@ static bool is_masked_watchpoint (const struct breakpoint *b); static int strace_marker_p (struct breakpoint *b); -/* The breakpoint_ops structure to be inherited by all breakpoint_ops - that are implemented on top of software or hardware breakpoints - (user breakpoints, internal and momentary breakpoints, etc.). */ -static struct breakpoint_ops bkpt_base_breakpoint_ops; - /* Breakpoints set on probes. */ static struct breakpoint_ops bkpt_probe_breakpoint_ops; @@ -14581,12 +14576,6 @@ initialize_breakpoint_ops (void) return; initialized = 1; - /* The breakpoint_ops structure to be inherit by all kinds of - breakpoints (real breakpoints, i.e., user "break" breakpoints, - internal and momentary breakpoints, etc.). */ - ops = &bkpt_base_breakpoint_ops; - *ops = vtable_breakpoint_ops; - /* Probe breakpoints. */ ops = &bkpt_probe_breakpoint_ops; *ops = vtable_breakpoint_ops;
reply other threads:[~2022-04-29 22:24 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220429222401.5C2763858434@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).