public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 00/23] More breakpoints cleanups
Date: Mon, 16 May 2022 19:40:07 +0100	[thread overview]
Message-ID: <20220516184030.665489-1-pedro@palves.net> (raw)

The main goal of this series was to eliminate init_raw_breakpoint.

It slowly tweaks a number of things to be able to do that.

Along the way, it converts the remaining init_foo functions to proper
ctors, and tweaks the class hierarchy a bit such that all code
breakpoints inherit from base_breakpoint.  In the end, it proposes
renaming base_breakpoint to code_breakpoint.

By inspection, I ran into a couple bugs around momentary breakpoints.
There are a couples patches in here to fix them.

I also noticed that nothing currently exercises the paths that make
create_breakpoints_sal actually create more than one breakpoint.  One
of the patches here is about adding a testcase for that.

See the individual patches for details.

Pedro Alves (23):
  add_location_to_breakpoint -> breakpoint::add_location
  Make structs breakpoint/base_breakpoint/catchpoint be abstract
  ranged_breakpoint: don't use init_raw_breakpoint
  ranged_breakpoint, use install_breakpoint
  ranged_breakpoint - move initialization to ctor
  Make a few functions work with base_breakpoint instead of breakpoint
  More breakpoint_ops parameter elimination
  Remove "internal" parameter from a couple functions
  init_breakpoint_sal -> base_breakpoint::base_breakpoint
  Make ada_catchpoint_location's owner ctor parameter be ada_catchpoint
  Convert init_ada_exception_catchpoint to a ctor
  Refactor set_internal_breakpoint / internal_breakpoint ctor
  Refactor momentary breakpoints, eliminate
    set_raw_breakpoint{,_without_location}
  Make exception_catchpoint inherit base_breakpoint instead of
    catchpoint
  Make breakpoint_address_bits look at the location kind
  Make catchpoint inherit breakpoint, eliminate init_raw_breakpoint
  Move common bits of catchpoint/exception_catchpoint to breakpoint's
    ctor
  Move add_location(sal) to base_breakpoint
  Add/tweak intro comments of struct breakpoint and several subclasses
  Momentary breakpoints should have no breakpoint number
  Make sure momentary breakpoints are always thread-specific
  Test "set multiple-symbols on" creating multiple breakpoints
  Rename base_breakpoint -> code_breakpoint

 gdb/ada-lang.c                     |  81 ++-
 gdb/break-catch-syscall.c          |   6 +-
 gdb/break-catch-throw.c            |  14 +-
 gdb/breakpoint.c                   | 805 ++++++++++++-----------------
 gdb/breakpoint.h                   |  93 ++--
 gdb/elfread.c                      |   6 +-
 gdb/mi/mi-cmd-break.c              |   4 +-
 gdb/minsyms.c                      |   4 +-
 gdb/python/py-finishbreakpoint.c   |   2 +-
 gdb/symtab.h                       |   5 +-
 gdb/testsuite/gdb.cp/ovldbreak.exp | 100 +++-
 11 files changed, 546 insertions(+), 574 deletions(-)


base-commit: e90601a4f1af82ff5350797ddc54e24efd731535
-- 
2.36.0


             reply	other threads:[~2022-05-16 18:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 18:40 Pedro Alves [this message]
2022-05-16 18:40 ` [PATCH 01/23] add_location_to_breakpoint -> breakpoint::add_location Pedro Alves
2022-05-16 18:40 ` [PATCH 02/23] Make structs breakpoint/base_breakpoint/catchpoint be abstract Pedro Alves
2022-05-16 18:40 ` [PATCH 03/23] ranged_breakpoint: don't use init_raw_breakpoint Pedro Alves
2022-05-16 18:40 ` [PATCH 04/23] ranged_breakpoint, use install_breakpoint Pedro Alves
2022-05-16 18:40 ` [PATCH 05/23] ranged_breakpoint - move initialization to ctor Pedro Alves
2022-05-16 18:40 ` [PATCH 06/23] Make a few functions work with base_breakpoint instead of breakpoint Pedro Alves
2022-05-16 18:40 ` [PATCH 07/23] More breakpoint_ops parameter elimination Pedro Alves
2022-05-16 18:40 ` [PATCH 08/23] Remove "internal" parameter from a couple functions Pedro Alves
2022-05-16 18:40 ` [PATCH 09/23] init_breakpoint_sal -> base_breakpoint::base_breakpoint Pedro Alves
2022-05-20 13:40   ` Lancelot SIX
2022-05-20 19:20     ` Pedro Alves
2022-05-16 18:40 ` [PATCH 10/23] Make ada_catchpoint_location's owner ctor parameter be ada_catchpoint Pedro Alves
2022-05-16 18:40 ` [PATCH 11/23] Convert init_ada_exception_catchpoint to a ctor Pedro Alves
2022-05-16 18:40 ` [PATCH 12/23] Refactor set_internal_breakpoint / internal_breakpoint ctor Pedro Alves
2022-05-16 18:40 ` [PATCH 13/23] Refactor momentary breakpoints, eliminate set_raw_breakpoint{, _without_location} Pedro Alves
2022-05-16 18:40 ` [PATCH 14/23] Make exception_catchpoint inherit base_breakpoint instead of catchpoint Pedro Alves
2022-05-16 18:40 ` [PATCH 15/23] Make breakpoint_address_bits look at the location kind Pedro Alves
2022-05-16 18:40 ` [PATCH 16/23] Make catchpoint inherit breakpoint, eliminate init_raw_breakpoint Pedro Alves
2022-05-16 18:40 ` [PATCH 17/23] Move common bits of catchpoint/exception_catchpoint to breakpoint's ctor Pedro Alves
2022-05-16 18:40 ` [PATCH 18/23] Move add_location(sal) to base_breakpoint Pedro Alves
2022-05-16 18:40 ` [PATCH 19/23] Add/tweak intro comments of struct breakpoint and several subclasses Pedro Alves
2022-05-16 18:40 ` [PATCH 20/23] Momentary breakpoints should have no breakpoint number Pedro Alves
2022-05-20 16:00   ` Tom Tromey
2022-05-20 19:25     ` Pedro Alves
2022-05-16 18:40 ` [PATCH 21/23] Make sure momentary breakpoints are always thread-specific Pedro Alves
2022-05-16 18:40 ` [PATCH 22/23] Test "set multiple-symbols on" creating multiple breakpoints Pedro Alves
2022-05-16 18:40 ` [PATCH 23/23] Rename base_breakpoint -> code_breakpoint Pedro Alves
2022-05-20 16:05   ` Tom Tromey
2022-05-20 16:06 ` [PATCH 00/23] More breakpoints cleanups Tom Tromey
2022-05-20 19:43   ` Pedro Alves

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=20220516184030.665489-1-pedro@palves.net \
    --to=pedro@palves.net \
    --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).