From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 0/5] Random cleanup patches
Date: Tue, 6 Feb 2024 12:14:22 -0500 [thread overview]
Message-ID: <20240206171514.119244-1-simon.marchi@efficios.com> (raw)
Here are some more preparatory patches that are in the series I'm
currently working on. I think they make sense on their own, so here
they are.
Simon Marchi (5):
gdb: add program_space parameter to mark_breakpoints_out
gdb: add inferior parameter to breakpoint_init_inferior
gdb: add program_space parameter to disable_breakpoints_in_shlibs
gdb: add program_space parameter to clear_solib
gdb: remove unnecessary nullptr check in remove_user_added_objfile
gdb/breakpoint.c | 35 +++++++++++------------------------
gdb/breakpoint.h | 22 ++++++++++++++++++----
gdb/corelow.c | 2 +-
gdb/infcmd.c | 10 +++++-----
gdb/infrun.c | 6 +++---
gdb/solib.c | 23 +++++++++++++----------
gdb/solib.h | 6 +++---
gdb/symtab.h | 4 ----
gdb/target.c | 4 ++--
gdb/windows-nat.c | 2 +-
10 files changed, 57 insertions(+), 57 deletions(-)
base-commit: 6fdf95ae532c61263e19e2036cfe3057bb928385
--
2.43.0
next reply other threads:[~2024-02-06 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 17:14 Simon Marchi [this message]
2024-02-06 17:14 ` [PATCH 1/5] gdb: add program_space parameter to mark_breakpoints_out Simon Marchi
2024-02-06 17:14 ` [PATCH 2/5] gdb: add inferior parameter to breakpoint_init_inferior Simon Marchi
2024-02-06 17:14 ` [PATCH 3/5] gdb: add program_space parameter to disable_breakpoints_in_shlibs Simon Marchi
2024-02-06 17:14 ` [PATCH 4/5] gdb: add program_space parameter to clear_solib Simon Marchi
2024-02-07 3:37 ` Simon Marchi
2024-02-06 17:14 ` [PATCH 5/5] gdb: remove unnecessary nullptr check in remove_user_added_objfile Simon Marchi
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=20240206171514.119244-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).