From: Eli Zaretskii <eliz@is.elta.co.il>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: confusion in the `b' command
Date: Mon, 22 Apr 2002 22:58:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020423095348.22959I-100000@is> (raw)
In-Reply-To: <87u1q3lb04.fsf@creche.redhat.com>
On 22 Apr 2002, Tom Tromey wrote:
> >>>>> "Eli" == Eli Zaretskii <eliz@is.elta.co.il> 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.
next prev parent reply other threads:[~2002-04-23 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 12:37 Tom Tromey
2002-04-22 13:13 ` Eli Zaretskii
2002-04-22 13:38 ` Tom Tromey
2002-04-22 22:58 ` Eli Zaretskii [this message]
2002-05-12 19:22 ` Daniel Jacobowitz
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=Pine.SUN.3.91.1020423095348.22959I-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=tromey@redhat.com \
/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