This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug cli/15570] New: Change default completer


http://sourceware.org/bugzilla/show_bug.cgi?id=15570

            Bug ID: 15570
           Summary: Change default completer
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: pmuldoon at redhat dot com

Possibly related http://sourceware.org/bugzilla/show_bug.cgi?id=7301

The default completer in GDB seems to be the location completer.  Even for
commands that have no completion utility:

IE  bt <tab>

Will invoke the location completer.  The location completer is also I suspect
the most expensive one in that:

1) It searches all symbols in all blocks for symbols matching <expression>
2) In doing the above, it expands all partial symbols (if I remember correctly,
partial symbols when expanded are replaced, not reconstructed, so in effect it
is the same cost as a full symbol read, load and parse).

The summary is actually a bit misleading.  Replacing the default completer
might not be the best way to proceed as it would require an audit of every
single command in GDB to ensure that some commands don't rely on locations
completion as default.  It might be better to write a null completer (or no
completions attached to a command, if GDB allows that) and selectively apply
those to the commands that make sense.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]