From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 00/12] Use intrusive_list for breakpoints and breakpoint locations
Date: Thu, 11 May 2023 10:48:20 -0400 [thread overview]
Message-ID: <20230511144832.17974-1-simon.marchi@efficios.com> (raw)
This series changes two linked lists to use intrusive_list. There are
some cleanups before that, and some small fixes that needed to be made
to some of our iterator wrappers.
Simon Marchi (12):
gdb: get gdbarch from syscall_catchpoint instead of location
gdb: make some breakpoint methods use `this`
gdb: constify breakpoint::print_it parameter
gdb: add breakpoint "has locations" methods
gdb: add breakpoint::first_loc methods
gdbsupport: add missing increment/decrement operators to
reference_to_pointer_iterator
gdb: link breakpoint locations with intrusive_list
gdb: remove bp_location_pointer_iterator
gdb: link breakpoints with intrusive_list
gdbsupport: make basic_safe_iterator::operator* return the same thing
as underlying iterator
gdbsupport: make filtered_iterator::operator* return the same thing as
underlying iterator
gdb: remove breakpoint_pointer_iterator
gdb/ada-lang.c | 20 +-
gdb/break-catch-exec.c | 4 +-
gdb/break-catch-fork.c | 4 +-
gdb/break-catch-load.c | 25 +-
gdb/break-catch-sig.c | 4 +-
gdb/break-catch-syscall.c | 21 +-
gdb/break-catch-throw.c | 10 +-
gdb/breakpoint.c | 1225 ++++++++++----------
gdb/breakpoint.h | 104 +-
gdb/dummy-frame.c | 4 +-
gdb/elfread.c | 8 +-
gdb/guile/scm-breakpoint.c | 4 +-
gdb/infrun.c | 11 +-
gdb/jit.c | 6 +-
gdb/python/py-breakpoint.c | 8 +-
gdb/python/py-finishbreakpoint.c | 8 +-
gdb/remote.c | 4 +-
gdb/solib-svr4.c | 10 +-
gdb/tracectf.c | 4 +-
gdb/tracefile-tfile.c | 4 +-
gdb/tracefile.c | 6 +-
gdb/tracepoint.c | 108 +-
gdb/tui/tui-winsource.c | 16 +-
gdbsupport/filtered-iterator.h | 7 +-
gdbsupport/reference-to-pointer-iterator.h | 18 +
gdbsupport/safe-iterator.h | 6 +-
26 files changed, 848 insertions(+), 801 deletions(-)
--
2.40.1
next reply other threads:[~2023-05-11 14:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 14:48 Simon Marchi [this message]
2023-05-11 14:48 ` [PATCH 01/12] gdb: get gdbarch from syscall_catchpoint instead of location Simon Marchi
2023-05-15 9:12 ` Alexandra Petlanova Hajkova
2023-05-11 14:48 ` [PATCH 02/12] gdb: make some breakpoint methods use `this` Simon Marchi
2023-05-15 13:12 ` Alexandra Petlanova Hajkova
2023-05-15 18:25 ` Simon Marchi
2023-05-11 14:48 ` [PATCH 03/12] gdb: constify breakpoint::print_it parameter Simon Marchi
2023-05-11 14:48 ` [PATCH 04/12] gdb: add breakpoint "has locations" methods Simon Marchi
2023-05-11 14:48 ` [PATCH 05/12] gdb: add breakpoint::first_loc methods Simon Marchi
2023-05-18 12:50 ` Andrew Burgess
2023-05-18 17:55 ` Simon Marchi
2023-05-24 13:00 ` Andrew Burgess
2023-05-11 14:48 ` [PATCH 06/12] gdbsupport: add missing increment/decrement operators to reference_to_pointer_iterator Simon Marchi
2023-05-11 14:48 ` [PATCH 07/12] gdb: link breakpoint locations with intrusive_list Simon Marchi
2023-05-18 14:44 ` Andrew Burgess
2023-05-18 18:40 ` Simon Marchi
2023-05-24 13:04 ` Andrew Burgess
2023-05-11 14:48 ` [PATCH 08/12] gdb: remove bp_location_pointer_iterator Simon Marchi
2023-05-11 14:48 ` [PATCH 09/12] gdb: link breakpoints with intrusive_list Simon Marchi
2023-05-11 14:48 ` [PATCH 10/12] gdbsupport: make basic_safe_iterator::operator* return the same thing as underlying iterator Simon Marchi
2023-05-11 14:48 ` [PATCH 11/12] gdbsupport: make filtered_iterator::operator* " Simon Marchi
2023-05-11 14:48 ` [PATCH 12/12] gdb: remove breakpoint_pointer_iterator Simon Marchi
2023-05-18 15:53 ` Andrew Burgess
2023-05-18 18:44 ` Simon Marchi
2023-05-18 20:59 ` Simon Marchi
2023-05-18 15:54 ` [PATCH 00/12] Use intrusive_list for breakpoints and breakpoint locations Andrew Burgess
2023-05-18 21:01 ` Simon Marchi
2023-05-25 14:01 ` 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=20230511144832.17974-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).