Re: [RFC] canonical linespec and multiple breakpoints ...

[Pedro Alves <pedro@codesourcery.com>]

On Tuesday 02 August 2011 18:08:46, Tom Tromey wrote:

> Pedro> I never replied to your patch, but my reaction was that it is
> Pedro> probably breaking breakpoints in the new inferiors today, even
> Pedro> without any linespec/multi breakpoints work.
> 
> Is there a way to set a breakpoint in a new inferior without first
> loading the debuginfo by hand?  It has been a while since I was looking
> at this, but I don't remember finding a way.
> 
> If there is one, though, I can easily test this.

If you set a breakpoint before the fork, the
breakpoint will end up with locations in the new inferior
after the fork.  Same if e.g., you set a breakpoint before
a fork/exec, and post-exec image happens to have
been compiled from the same code (file:lineno) as the 
original breakpoint's location was resolved to.  I was
under the impression your patch would make it so 
the new inferior would no longer stop for these breakpoints.

> Pedro> What I don't think I have seen addressed is how the proposal
> Pedro> interacts with multi-exec.  E.g, suppose I have program foo
> Pedro> loaded once (one inferior) and program bar loaded twice (two
> Pedro> inferiors).  I have one of the bar inferiors in focus, 
> Pedro> and I do "b main".  How many locations does this resolve to?
> Pedro> One, two, or three?  Currently, it resolves to two.
> 
> Three, following the rule that a breakpoint will fire at all matching
> locations.

Okay.

-- 
Pedro Alves