Re: Filename with "./" in breakpoint command

[Bob Rossi <bob@brasko.net>]

On Mon, Dec 05, 2005 at 11:55:18PM -0500, Daniel Jacobowitz wrote:
> On Tue, Dec 06, 2005 at 06:27:37AM +0200, Eli Zaretskii wrote:
> > > Date: Mon, 5 Dec 2005 13:55:56 -0500
> > > From: Daniel Jacobowitz <drow@false.org>
> > > Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
> > > 
> > > Or, when the existing lookups have failed for a relative pathname,
> > > canonicalize it and treat it like a full path?
> > 
> > I don't like that, since it requires to chdir to some directory first.
> 
> Could you explain why not?  GDB already has a notion of $cdir, and it
> seems logical to me that if the user types "./foo.c" they mean for that
> to be relative to $cdir, but I certainly could be missing something.

I also don't think it makes sense to prompt the user on this issue.
However, unless I'm missing something, I don't think it makes sense to
set multiple breakpoints.

If the user types 'b ./foo.c' then that maps to exactly 1 file. If the
file can be found, we could set the breakpoint. If the file can not be
found, then we should give the error that there is no such file.

Bob Rossi