This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug exp/21827] Regression: gdb command lookup became case-insensitive
- From: "source-ware at trk dot nickurak.ca" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 24 Jul 2017 20:02:28 +0000
- Subject: [Bug exp/21827] Regression: gdb command lookup became case-insensitive
- Auto-submitted: auto-generated
- References: <bug-21827-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21827
--- Comment #1 from Jeremy Nickurak <source-ware at trk dot nickurak.ca> ---
simark from IRC pointed out this change as the source of the regression via
bisection:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=3d7b173c29900879c9a5958dd6029fd36666e57c
As well as this this thread:
https://sourceware.org/ml/gdb-patches/2017-01/msg00157.html
A couple thoughts:
* If this backwards-incompatible change is desired, it should probably be in
the release-notes.
* If case-sensitivity is the desired behavior here, one should probably be able
to define a command with a specified case. In my example here, I've specified
some upper-case letters in the name of my definition, but it was converted to
lowercase at define-time.
--
You are receiving this mail because:
You are on the CC list for the bug.