This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] fix for checking the command ambiguousness.
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Muhammad Bilal <mbilal at codesourcery dot com>, "gdb-patches\ at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Thu, 07 Nov 2013 07:53:09 -0700
- Subject: Re: [patch] fix for checking the command ambiguousness.
- Authentication-results: sourceware.org; auth=none
- References: <521C6FDD dot 3090909 at codesourcery dot com> <521CEB86 dot 7060106 at redhat dot com> <521DB1E1 dot 5040804 at codesourcery dot com> <521DE287 dot 2010208 at redhat dot com> <521E0673 dot 5080007 at codesourcery dot com> <522728B9 dot 5000103 at codesourcery dot com> <522EF552 dot 1090607 at codesourcery dot com> <5238833A dot 9080902 at codesourcery dot com> <523883F4 dot 5070207 at redhat dot com>
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> As the test uses Python stuff to expose the bug, I'd appreciate
Pedro> it if a Python person took a look.
Pedro> Is this only triggerable with Python? If so, why?
I looked, and there aren't many callers of lookup_cmd_composition:
maintenance_do_deprecate, deprecated_cmd_warning, and gdbpy_parameter.
The last one is the path the test case takes.
Tom