Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: remove global stop_bpstat dependency from breakpoints module
Date: Thu, 05 Jun 2008 18:34:00 -0000	[thread overview]
Message-ID: <20080605183347.GD16610@caradoc.them.org> (raw)
In-Reply-To: <200806051927.07953.pedro@codesourcery.com>

On Thu, Jun 05, 2008 at 07:27:07PM +0100, Pedro Alves wrote:
> As I said, I would mind at all to change this to the read
> the PC of the current thread.  Just pointing out the current
> behaviour.

I think that would be correcting it to the right behavior.  In 99% of
the cases where this is used at all, they mean the same thing.

> > > One way to fix it, would be to also loop through all threads to update
> > > their version of stop_bpstat, but I'd like better.
> >
> > If we do need to context-switch stop_bpstat, it seems like checking
> > all of those would be simpler than this patch as posted.
> 
> Well, simpler yes, but adds even more coupling.  I thought this was
> a nice cleanup.  It's mentioned a few times in comments
> throughout breakpoints.c.

I don't like reference counting as a solution to clear memory
management.  Sometimes it's necessary or helpful, but here I think it
just gives us room to be careless (and have to worry more about
leaks).

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-06-05 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 11:41 Pedro Alves
2008-06-05 18:03 ` Daniel Jacobowitz
2008-06-05 18:27   ` Pedro Alves
2008-06-05 18:34     ` Daniel Jacobowitz [this message]
2008-06-05 18:46       ` 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=20080605183347.GD16610@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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