This is the mail archive of the
mailing list for the GDB project.
Re: confusion in the `b' command
- From: Eli Zaretskii <eliz at is dot elta dot co dot il>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 23 Apr 2002 09:57:10 +0300 (IDT)
- Subject: Re: confusion in the `b' command
On 22 Apr 2002, Tom Tromey wrote:
> >>>>> "Eli" == Eli Zaretskii <firstname.lastname@example.org> writes:
> Eli> What version of GDB is that? Head? branch? released version?
> Latest cvs trunk gdb. (That was in my email, albeit buried a bit.)
Yes, it was buried, sorry for not paying attention.
It's probably a good idea to see if that isn't some regression due to
latest changes. I have several versions of GDB going back as far as
4.18, but unfortunately I have no gcj installed anywhere.
> >> * Second, that b 'x.main' would work anyway, since it is unambiguous.
> Eli> I'm not sure what you mean here. Do you mean that GDB shouldn't have
> Eli> forced you to quote the string "x.main(java.lang.String)"?
> I shouldn't even have to type `(java.lang.String)' at all.
> `b x.main' is unambiguous. There is only one `main' method in the
> class `x'.
I think the punctuation characters prevent that. But it could also be a
bug or regression. One possible way to find out is to try this with
commands that complete only on symbols (`b' completes on ``locations'',
which could include file names and line numbers, so it's more complicated
and thus more bug-prone).
Sorry I can't do that myself, for the lack of gcj.