Crash in 22.0.0.8

[rowbearto]

Got a crash last night while doing a long build in SE 22.0.0.8. Log is attached.

I had 2 instances of SE running, both doing very long builds. One of the SE instances crashed, the other did not. I happened to catch some prints in one of my windows, but I don't know which directory the core file is in. It would be useful if SE could print the directory where the core file will likely be upon a crash.

[patrick]

Ok, we'll work with what's in the log, and see what we can find.  That particular malloc error may narrow down the possibilities at least.  Thanks for the report.

[patrick]

What are the command line parameters you're running the two instances of SlickEdit with?

[rowbearto]

nohup /home/rbresali/pen/slickedit/se_latest_64/bin/vs -st 0 -sc /home/rbresali/pen/slickedit/config  >> ~/logs/se.log 2>&1 &
nohup /home/rbresali/pen/slickedit/se_latest_64/bin/vs -st 0 -sc /home/rbresali/pen/slickedit/config +new >> ~/logs/se.log 2>&1 &

[Dennis]

It might also be helpful to see the error output from the long build (if at all possible).  The crash could be related to error parsing and/or populating the Message List tool window.

[rowbearto]

I uploaded the build log that was going on when it crashed - good thinking. Maybe you can reproduce the issue by doing "cat log" and see if the error parsing crashes? I save the output of all my builds to logfiles, and I also have the logs from all the builds before this if you are interested. I've done this long build many times before, and the other instance was a very similar one, so SE has handled it before. Good thinking to ask for this.

If you still can't reproduce, I do have some custom error parsers defined, so we can try that if you can't reproduce.