core dump in 22.0.2 linux x64 March 12 2018

[rowbearto]

I have a macro that I use to scan a directory structure, automatically add files to a project, and then it gets tagged.

This macro has been working really well, except for one project where I get a consistent core dump when SE is performing the tagging of the files in the project.

I uploaded the core dump file to support.slickedit.com as core_180312.7z.

The macro that I use for adding the files to the project is on github here:

https://github.com/rbresalier/sync_project_with_scm

I see that it gets a segfault when I see the progress bar for the tagging and the progress bar is maybe about 5% through.

Unfortunately I can't share the whole project as it is proprietary, it has python, perl and cfg (ini format) files.

I'm on Linux x64 CentOS 7.

Thanks for taking a look!

[rowbearto]

Looks like SE is choking when trying to tag one of the perl files (*.pl or *.pm), when I have only the *.py and *.cfg files in the project, the tagging does not crash. When I have only the *.pl and *.pm files (and no *.py; *.cfg), it crashes. It could take me a while to narrow down which file is causing SE to crash, but if that info is in the core dump it could speed things up.

[rowbearto]

hmm, after playing around, the crashing on *.pl files has seem to have gone away, can't reproduce at the moment. Maybe not tied to tagging a particular file. Maybe you can get some info from the core dump.

[patrick]

Hmm, I thought we did a fix for this, but maybe didn't send it out.  Let me look back at the changes.  It wouldn't be a hotfix, we'd have to send you an updated vs_exe to test whether you crashed anymore.

[patrick]

I must be wrong, the fix that I thought went with that stack trace was already in 22.0.2.  I'll need to take a closer look then.  False alarm.

[rowbearto]

ok, I am able to reproduce this again now. If I have enough time sometime, I may be able to make a package that I can share that will reproduce it so SlickTeam can investigate, but I don't have the time to do that now.

[rowbearto]

I was able to create a reproducible test case. Uploaded to support.slickedit.com a file called core_180312.tar.gz (as support case core_180312).

I could not reproduce with a clean config, so my config directory - 22.0.2 is included in the test case.

Instructions to reproduce:

1) Lauch SE with my config dir - 22.0.2
2) Load the workspace - prj/aptldr.vpw
3) Load the macro - prj/sync_project_with_scm.e (maybe my "ssync" macro is already defined in the 22.0.2 config directory, so this step not needed?)
4) Run the command: "ssync" which was in the defined in the macro. It scans the directory structure for files to add to the project, then adds them and initiates tagging.
5) Observe crash during tagging

[rowbearto]

Patrick, SlickTeam: Just curious if you had the time to try and reproduce this yet, and if so if you reproduced it?

[patrick]

I can get it to crash with your setup.  I don't have anything for you yet, I'll let you know when I do.

[patrick]

We're working on a fix for this.  Once it's ready, we'll need to build a vs_exe for you to try it out, it's not something that can be hotfixed.

[rowbearto]

Thanks. Is there any particular option in my config that is triggering it? It doesn't crash with a clean config.

[patrick]

No, the error isn't configuration related.  For us, when we'd pinned down what file was being processed at the time of the crash, it was hard to reproduce, and was very dependent on what files were processed, and in what order.  In the end we lucked up with an initial configuration for the project that was consistent enough to let us debug.