Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org, Matt Rice <ratmice@gmail.com>,
	Stan Shebs <stanshebs@earthlink.net>
Subject: Re: Toward multicore GDB - Set theory
Date: Tue, 08 Nov 2011 15:45:00 -0000	[thread overview]
Message-ID: <201111081544.40334.pedro@codesourcery.com> (raw)
In-Reply-To: <m3zkg6k662.fsf@fleche.redhat.com>

On Tuesday 08 November 2011 15:03:33, Tom Tromey wrote:

> I think this is going to interact with my ambiguous breakpoint /
> linespec changes.  At various points in the new code, linespec iterates
> over program spaces; this should be filtered according to the trigger
> set.  I am wondering whether you are basing your work on this patch set,

I'm currently working against current pristine mainline.

> and if not, how we can best manage the changes.  I would rather not be
> in a race to finish, but instead talk about how we can best cooperate.

My changes aren't as near complete as yours, so I don't think
there's much chance for me to win such a race.  :-)  But note
I haven't done anything like making:

  [2.*:3.*] break main

look for `main' in inferiors 2 and 3, and I don't plan to.  I'm leaving
the symbol search side out, as we'll get most of that from your
changes, with some kind of extra filtering.

There's a bunch left to try/do that doesn't touch linespec / symbol
filtering.  So I have absolutely no problem with seeing your changes
go in, and picking them up that way.  If I get further enough in
progress before your patch lands, I'll rebase on top of it.

I'll try to post the WIP code somewhere soon, so you (all) can
take a look.

-- 
Pedro Alves


      reply	other threads:[~2011-11-08 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02  0:04 Stan Shebs
2011-11-03 21:01 ` Tom Tromey
2011-11-04 13:20   ` Pedro Alves
2011-11-07 17:38   ` Joel Brobecker
2011-11-08  1:14     ` Daniel Jacobowitz
2011-11-08  5:17   ` Matt Rice
2011-11-08 14:50     ` Pedro Alves
2011-11-08 15:04       ` Tom Tromey
2011-11-08 15:45         ` Pedro Alves [this message]

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=201111081544.40334.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=ratmice@gmail.com \
    --cc=stanshebs@earthlink.net \
    --cc=tromey@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