Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 3/3] bpstat_what removal
Date: Tue, 04 May 2010 14:10:00 -0000	[thread overview]
Message-ID: <4BE02AB0.6060609@codesourcery.com> (raw)
In-Reply-To: <20100503200217.GD30386@host0.dyn.jankratochvil.net>

Jan Kratochvil wrote:
> Hi,
>
> the simple idea is to inline bpstat_what into handle_inferior_event.  This
> removes enum bpstat_what_main_action and struct bpstat_what currently acting
> just as an interface between these two functions.
>   
There's a reason for this actually, which is that it helps keep the 
myriad of random breakpoint types from infecting the rest of GDB.  
Breakpoint types are visible globally, and individual breakpoint types 
are mentioned here and there in the code, but I think it's worthwhile to 
keep the type enumerations / switches in breakpoint.c as much as possible.

There is a pretty good chance that we're going to be doing some 
refactoring on how breakpoint types are handled - people are interested 
in the idea of "tracing watchpoints" (or "watching tracepoints" :-) ) 
for instance - so there's a practical reason to provide interfaces that 
define the net effect of types, rather than requiring callers to know 
aracane details of each.

Stan


  reply	other threads:[~2010-05-04 14:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 20:02 Jan Kratochvil
2010-05-04 14:10 ` Stan Shebs [this message]
2010-05-07 16:17   ` Jan Kratochvil
2010-05-07 16:26     ` Pedro Alves
2010-05-07 17:02       ` Jan Kratochvil
2010-05-07 17:17         ` Pedro Alves
2010-05-17 21:46           ` Jan Kratochvil
2010-06-12 17:02             ` [patch 3/3] bpstat_what removal [rediff] Jan Kratochvil
2010-06-15 15:08               ` Pedro Alves
2010-06-15 21:54                 ` Jan Kratochvil
2010-06-16 19:13                   ` Pedro Alves
2010-06-18 10:41                     ` Jan Kratochvil
2010-06-18 11:42                       ` Pedro Alves
2010-06-18 14:09                         ` Jan Kratochvil
2010-06-18 14:35                           ` Pedro Alves
2010-06-24 14:44                     ` [patch 3/3] bpstat_what removal Jan Kratochvil
2010-06-24 14:48                       ` [patch 3.1/3] bpstat_what removal - addon gdb_assert Jan Kratochvil
2010-06-24 15:03                       ` [patch 3/3] bpstat_what removal Pedro Alves
2010-06-24 15:21                         ` Jan Kratochvil
2010-06-16 20:40                   ` [patch 3/3] bpstat_what removal [rediff] Tom Tromey
2010-06-23 14:42                     ` Jan Kratochvil

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=4BE02AB0.6060609@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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