'find symbol' (f) command sometimes just stops working

[timur]

I'm using v16 on Linux, and recently I've discovered a new bug that's hard to reproduce and debug.

Every now then, without warning, the 'find symbol' command just stops working.  For example, right now I go to the command line, and start typing:

f get_sys

at this point, there's a short list displayed that shows:

get_sys_info(func)
get_sys_info(proto)
get_sys_reg_addr(define)
get_syscfg_reg(func)

If I select the first one and press enter, nothing at all happens.  No cursor movement, no dialog boxes, no message.  Nada.  The command prompt closes and I'm back in the editing window, nowhere near the get_sys_info() function.  This only happens with some symbols, though.

If I go back to the command line and press up-arrow (to recall the command), and press enter again -- the same thing.  If I close and re-open the project, it's still broken.  If I close and re-open Slickedit itself, it's still not working.  If I close the project, delete the .vtg file, and reopen the project, it still doesn't work.

If I manually open the file that contains function get_sys_info(), and I put the cursor on that function and press ctrl-., I get a dialog box asking me to select the symbol from a list.

So Slickedit knows about the symbol, it just refuses to let me jump to it via the 'f' command. 

Now, if I do this:

f debug

that works just fine.  So why does Slickedit not like some symbols?

[timur]

I've done a little more experimentation.  I think it's the "(func)" after the symbol name that's confusing it.  If I manually type in

f get_sys_info

and press enter, then I get a dialog box asking me to pick an instance of this symbol.  But if I do:

f get_sys_info(func)

it's broken.

[timur]

I think I found the culprit: "Use strict case-sensitivity rules".  When I enable this option, the 'f' command rejects "f get_sys_info(func)".  When I turn that off, it works.

I turned the feature on because the C language is case-sensitive.

[Matthew]

Thanks for the detailed information. We're currently investigating this.

[Dennis]

Thanks for the tip.

The next revision of the cumulative hot fix will have a fix for this.

[SlickEdit Support]

The hotfix has been updated, and this fix should be included.