SpartanJ
commented
2 months ago Hi, that's not a crash. You built the library and ecode in debug mode and triggered an special assert that triggers a breakpoint, it triggered here, app wouldn't have crashed, but some asserts are there to identify potential issues and unexpected behaviours like this one: it was trying to access a line that doesn't exists anymore in the document during a lookup for links over the cursor position, but knows how to handle the situation and avoids any crash gracefully. Problem is that if you're not debugging it process will be paused forever since you don't have any way to continue after the breakpoint. I guess this breakpoint can trigger if you paste you contents into a selection that contains less lines that the original selection and the mouse is positioned in a position that was occupied before but not used now (I'll try to trigger it later, but it's nothing problematic).
Please don't use ecode in debug mode (I guess you manually built ecode and didn't use the build script provided), it's much slower and you'll encounter several breakpoint calls all over the code base, it's not meant to be used by users, just developers. As a reminder, to build in release mode if you used premake5 during make call you need to add make config=release_x86_64, and if used premake4 just use make config=release.
I'll add this information in the eepp README, since it's only mentioned on some OSes but not all.
Curculigo
I build from the latest code. It seems the newly merged
esfwis not OK.Description: A CMakeLists.txt file again. I'm selecting the code to paste into other CMakeLists.txt file and crashed. The files were dragged into ecode from Windows Explorer. They are not even on the list of recent files the next time I start ecode this time.