SE 22.0.0.9 crash when search replace "kill" with "kill -9"

[rowbearto]

Open the attached file in SE.

Using BigFind/Replace, search "kill" and replace with "kill -9". Press "Go", SE crashes

[mjdl]

FYI: On SE 22.0.0.8 x64 on Windows 7 x64, search/replace operation on your file succeeds.

[rowbearto]

Yeah and it worked for me too on Windows 7 x64 with 22.0.0.9

It may be particular to Linux (I'm in Centos) or particular to my configuration.

If SE team can't reproduce on Linux, I will send my configuration.

[rowbearto]

I uploaded my config to support.slickedit.com under "killdashninecrash".

[Clark]

Replace completes fine for me after I've imported your config on Ubuntu. I wouldn't expect a feature like this to be dependent on a particular Linux distrib.

Can you reproduce this with a clean config on Linux? If not, can you reproduce this with a clean config after importing the options you've uploaded?

[rowbearto]

I tried this in the VM I created for you for the other issue. SE does not crash there. So I don't know what is special about the setup I have where it crashes. I can't seem to get crash dumps out - I'll try a little more to get crash dumps.

[rowbearto]

I found a way to reproduce this reliably in the CentOS virtual machine that I sent for the other issue.

First, modify (you can run SE using typing "vsl" at konsole promtp) the /home/setest/pen/bin/vsl file, change line 82 from:

SE_CONFIG_DIR="${SE_CONFIG_PARENT_DIR}/config2"

to

SE_CONFIG_DIR="${SE_CONFIG_PARENT_DIR}/config"

(basically change from "config2" to "config" directory).

Exit SE and relaunch it by typing "vsl" at konsole prompt.

In the "Search" window (not search/replace), check both the "list all occurrences" and "List current context" box. This is important to reproduce the issue.

Then, open the "tst" file, go into the Replace window and do the search "kill" and replace with "kill -9" and then do "go"

This causes SE to crash every time.

[Clark]

Reproduced. You need just the right combination of options. I can reproduce this on Windows. You must have "List current context" AND "List replaced matches" checked AND be editing a file which has a proc_search function for listing context (instead of a C++ implementation). "Wrap at beginning/end" doesn't need to be checked.

[rowbearto]

Glad that you found it!