Summary: | Regression: gdb command lookup became case-sensitive; but definitions are forced into lowercase | ||
---|---|---|---|
Product: | gdb | Reporter: | Jeremy Nickurak <source-ware> |
Component: | exp | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | brobecker, simark |
Priority: | P2 | ||
Version: | 8.0 | ||
Target Milestone: | 8.0.1 | ||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
Jeremy Nickurak
2017-07-24 16:08:49 UTC
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. Other strange things that come out of this; The following gdb snippet fails unexpectedly:
define myFunction
print "hello"
end
document myFunction
Just a dummy test function
end
->
Type "apropos word" to search for commands related to "word".
(gdb) define myFunction
Type commands for definition of "myFunction".
End with a line saying just "end".
> print "hello"
>end
(gdb) document myFunction
Undefined command: "myFunction". Try "help".
Also pushed to the gdb-8.0-branch in time for the 8.0.1 release. So adjusting the target milestone accordingly. https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=95eeca3bccb6121c201183e21cb5fc39a6b711a2 |