Increase Slick-C stack size?

[Kork]

Hi, in Slick Edit (SlickEdit 2013 (v18.0.1.2 64-bit)), I am searching files in absolutely monster trees with many deep folders.

I often get a bug out with "Slick-C Error" expression stack overflow, file=stdcmds.ex offset=4217 in a popup and another popup that looks like a stack dump.  The stack dump has lines from 0 to 1020, so it looks suspiciously like a 1024 limit.

How can I bump this up to 2048, or 9 billion, so I can complete the search?

[Graeme]

What operating system are you using?

Just a quick suggestion - if you can't find a solution maybe you could run sgrep externally from the build window.
dos("-e sgrep DEBUG *.c");

or trial the latest release of slickedit.

[Marcel]

Alternatively, write a directory traversal algorithm that doesn't use recursion. A simple array as a push/pop stack should do the trick.

[Kork]

dos("-e sgrep DEBUG *.c");

"Unknown command"

I am assuming it is starting sgrep, which I probably don't have.


(Also, I cannot tell if the previous poster is being sarcastic to SlickEdit or not, but I am using SlickEdit's find in files function, apparently itself written in Slick C.)

[Graeme]

Sorry I was rushing.  sgrep.exe is in the slickedit installation "win" folder.  Type sgrep in the build window and you'll see how to use it.

You might be able to use FindIn-xgrep.e from here - see the runsg command.  It probably needs some changes to be useful.
https://community.slickedit.com/index.php/topic,9599.msg41046.html#msg41046

If you want you could try opening stdcmds.e from the slick installation macros folder.  Then on the slick command line type
st -f 4217
and it will take you to the line of slick c code that caused the error.  Could you then post the function that had the error and identify which line had the error?  I'm curious to know what an expression stack is.

By the way, I think Marcel was making a serious suggestion but I would have expected that the slick search was handled entirely in the core of slickedit and not in slick C.  There is a slick c "file_match" function that does directory searching though.

[Dennis]

@Kork:  You might want to verify that your monster directory tree is actually over 1000 levels deep, and that your code is not traversing the same directory recursively, due to a bug or a symbollic link (if the directory is remote mounted from Linux or macOS).

Generally, if you get a Slick-C stack, it is helpful to attach the contents of the Stack when reporting the problem, as well as your user-written code.  We really have very little idea what API's you are using.

[Kork]

Generally, if you get a Slick-C stack, it is helpful to attach the contents of the Stack when reporting the problem, as well as your user-written code.  We really have very little idea what API's you are using.

Again, I am not using any APIs or Slick-C.  I am using SlickEdit's built-in Find in Files function, Search menu -> Find in Files...

[Dennis]

Open <config>/logs/stack.log, and attach that here.  However, before doing that, you should verify that you still get the problem with the current version of SlickEdit.