public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Pedro Alves <palves@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Remove "internal" parameter from a couple functions Date: Fri, 20 May 2022 19:43:03 +0000 (GMT) [thread overview] Message-ID: <20220520194303.E3CAE3830880@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d837fd813d9c72ea7d06ef839b95857dcf0da811 commit d837fd813d9c72ea7d06ef839b95857dcf0da811 Author: Pedro Alves <pedro@palves.net> Date: Sat May 7 00:07:44 2022 +0100 Remove "internal" parameter from a couple functions None of init_breakpoint_sal, create_breakpoint_sal, and strace_marker_create_breakpoints_sal make use of their "internal" parameter, so remove it. Change-Id: I943f3bb44717ade7a7b7547edf8f3ff3c37da435 Diff: --- gdb/breakpoint.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index 7008672e784..dd6623dd6b5 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -8305,7 +8305,7 @@ init_breakpoint_sal (base_breakpoint *b, struct gdbarch *gdbarch, enum bptype type, enum bpdisp disposition, int thread, int task, int ignore_count, int from_tty, - int enabled, int internal, unsigned flags, + int enabled, unsigned flags, int display_canonical) { int i; @@ -8462,7 +8462,7 @@ create_breakpoint_sal (struct gdbarch *gdbarch, type, disposition, thread, task, ignore_count, from_tty, - enabled, internal, flags, + enabled, flags, display_canonical); install_breakpoint (internal, std::move (b), 0); @@ -12152,7 +12152,7 @@ strace_marker_create_breakpoints_sal (struct gdbarch *gdbarch, std::move (extra_string), type_wanted, disposition, thread, task, ignore_count, - from_tty, enabled, internal, flags, + from_tty, enabled, flags, canonical->special_display); /* Given that its possible to have multiple markers with the same string id, if the user is creating a static
reply other threads:[~2022-05-20 19:43 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=20220520194303.E3CAE3830880@sourceware.org \ --to=palves@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).