Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [0/6] breakpoints_ops for all kinds of breakpoints
Date: Fri, 22 Jul 2011 15:42:00 -0000	[thread overview]
Message-ID: <201107221640.25105.pedro@codesourcery.com> (raw)

I did yet a bit more work on:

 <http://sourceware.org/ml/gdb-patches/2011-06/msg00374.html>

This converts all breakpoint kinds to the breakpoint_ops
mechanism.

IMO, this is committable as is.  WDYT?

There's a lot left to do still.  E.g.: The print_one method
is still left behind; insert/removal could do with better
abstracting; a lot of tangling revealed by the need for 
special checks of tracepoint/watchpoint types at inner layers
of breakpoint creation; there are many places that still
switch on the breakpoint's type, as there's no breakpoint_ops
equivalent for what they're doing.

No regressions for me, native or gdbserver x86_64-linux.

-- 
Pedro Alves


             reply	other threads:[~2011-07-22 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 15:42 Pedro Alves [this message]
2011-07-22 17:33 ` Tom Tromey
2011-07-25 12:39   ` Pedro Alves
2011-07-25 16:20     ` Tom Tromey
2011-07-22 17:38 ` Phil Muldoon
2011-07-25 14:17   ` Pedro Alves
2011-07-25 14:40     ` Phil Muldoon

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=201107221640.25105.pedro@codesourcery.com \
    --to=pedro@codesourcery.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