Re: Filename with "./" in breakpoint command

[Daniel Jacobowitz <drow@false.org>]

On Wed, Dec 07, 2005 at 10:46:54AM +0300, Vladimir Prus wrote:
> > Vladimir's original report is for communication from an IDE to GDB.
> > "Find the best match" and "ask the user" aren't very helpful; the IDE
> > needs to unambiguously specify what file it's already opened and is
> > showing to the user, in a way that GDB can understand precisely what
> > file is meant.  Absolute pathnames seem awfully convenient for that.
> 
> Yes. I've just suggested that not supporting relative paths can be not very
> convenient for those directly using console interface. Especially when you
> say "break ./tracepoint.cpp:NNN", gdb suggests that this file might be in
> shared library that's no loaded yet, which can confuse users even more.
> 
> I think either:
> 
>    1. Relative paths should be handled fine, or
>    2. Relative paths should produce a warning from gdb.

I'd rather #1.  But, there's a lot of room for what "fine" is. 
Relative only to $cdir?  Relative to the directory search path?

> > For a user typing "break foo.c:54" we've already agreed on a more
> > useful behavior - though no promises when it will be implemented!
> 
> Which one is that? Setting breakpoint on each file matching foo.c, or
> prompting?

Multiple breakpoints.

-- 
Daniel Jacobowitz
CodeSourcery, LLC