aboutsummaryrefslogtreecommitdiffstats
path: root/server
diff options
context:
space:
mode:
authorblasty <blasty@local>2026-07-25 21:19:26 +0200
committerblasty <blasty@local>2026-07-25 21:19:26 +0200
commitb79d1028b0365b02e8d7d515087482e2ee249d6a (patch)
tree6a1bcb869aba26260018e48d505735afcd17dbdd /server
parenthighlight: bring pseudocode onto the measured palette (diff)
downloadida-tui-b79d1028b0365b02e8d7d515087482e2ee249d6a.tar.gz
ida-tui-b79d1028b0365b02e8d7d515087482e2ee249d6a.tar.xz
ida-tui-b79d1028b0365b02e8d7d515087482e2ee249d6a.zip
palette: match case-insensitively in BOTH directions
Ctrl+N found nothing on libcrypto. Typing "PEM_read_bio" returned 0 of 10093 functions while the backend resolved the very same name to 0x1d6290. _fuzzy lowercased the NAME but not the QUERY, then walked the query's characters through the lowered name. One capital letter and the subsequence walk fails at the first character, so the match is not merely worse — it is None, and the palette shows nothing at all. Invisible on the test binary because C symbols there are lowercase (main, strlen, error) and every existing palette check typed a lowercase query. Fatal on any library that capitalises: OpenSSL, most SDKs, Windows binaries. The paging index was the obvious suspect and was innocent — all_loaded() had all 10093. Verified on a live libcrypto pane: "PEM_read_bio" now returns 34 hits, exact match ranked first. tests: the palette scenario now types "MAIN" and expects "main". Confirmed it fails without the fix (results=[]) and passes with it. 193/0.
Diffstat (limited to 'server')
0 files changed, 0 insertions, 0 deletions