From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Filename with "./" in breakpoint command
Date: Tue, 06 Dec 2005 20:13:00 -0000 [thread overview]
Message-ID: <uvey2kmq5.fsf@gnu.org> (raw)
In-Reply-To: <20051206115559.GA20190@white> (message from Bob Rossi on Tue, 6 Dec 2005 06:55:59 -0500)
> Date: Tue, 6 Dec 2005 06:55:59 -0500
> From: Bob Rossi <bob@brasko.net>
>
> 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.
We are miscommunicating: multiple breakpoints were suggested for the
situation where the user types "b foo.c" and there are more than 1
file in the symtabs whose basename is foo.c.
next prev parent reply other threads:[~2005-12-06 20:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 12:58 Vladimir Prus
2005-12-03 14:17 ` Eli Zaretskii
2005-12-03 14:22 ` Bob Rossi
2005-12-03 14:55 ` Eli Zaretskii
2005-12-03 15:01 ` Bob Rossi
2005-12-05 6:53 ` Vladimir Prus
2005-12-05 18:39 ` Eli Zaretskii
2005-12-05 18:56 ` Daniel Jacobowitz
2005-12-06 4:27 ` Eli Zaretskii
2005-12-06 4:55 ` Daniel Jacobowitz
2005-12-06 11:56 ` Bob Rossi
2005-12-06 14:01 ` Joel Brobecker
2005-12-06 14:26 ` Andrew STUBBS
2005-12-06 20:13 ` Eli Zaretskii [this message]
2005-12-06 20:11 ` Eli Zaretskii
2005-12-06 20:17 ` Daniel Jacobowitz
2005-12-06 21:02 ` Eli Zaretskii
2005-12-06 21:09 ` Daniel Jacobowitz
2005-12-06 22:32 ` Eli Zaretskii
2005-12-07 7:49 ` Vladimir Prus
2005-12-07 14:51 ` Daniel Jacobowitz
2005-12-07 16:46 ` Vladimir Prus
2005-12-08 20:53 ` Paul Gilliam
2005-12-03 14:19 ` Bob Rossi
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=uvey2kmq5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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