This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/196: completer bugs
- To: nobody at sources dot redhat dot com
- Subject: Re: gdb/196: completer bugs
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- Date: 17 Aug 2001 08:48:04 -0000
- Cc: gdb-prs at sources dot redhat dot com,
- Reply-To: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
The following reply was made to PR gdb/196; it has been noted by GNATS.
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: fnasser@cygnus.com
Cc: keiths@cygnus.com, gdb-gnats@sources.redhat.com
Subject: Re: gdb/196: completer bugs
Date: Fri, 17 Aug 2001 11:38:07 +0300
> Date: Thu, 16 Aug 2001 17:43:25 -0400
> From: Fernando Nasser <fnasser@cygnus.com>
> >
> > >Description:
> > Symbol completion appears to be slightly broken. It often
> > includes things like type names in the symbol list.
> > >How-To-Repeat:
> > 1) Load gdb into gdb
> > 2) At prompt type "break comple<TAB><TAB>" and look at
> > what comes out:
> > (gdb) break comple
> > complete.c completedieinfo
> > complete_command completer.c
> > complete_execution completer.h
> > complete_object_allocating_ctor completion_changed_buffer
> > complete_object_ctor completion_list_add_name
> > complete_object_dtor completion_matches
> > complete_on_cmdlist complex double
> > complete_on_enum complex float
> > complete_symtab complex int
> > completed.1 complex long double
> > (gdb) break comple
> >
> > "complex long double"? completed.1? complete.c?
completed.1, completer.c, complete.c, etc. are present in this list
because you might have meant something like "break complete.c:1234".
This feature was added (by yours truly) a couple of months ago; it
makes the life quality of this completion junky much better ;-)
> Maybe we could have a linespec_completer() and some other more
> specific completers so the list gets shorter.
You mean, like completer.c:location_completer? ;-)