[cannot repeat] GTK2 Access Violation Still Happens

[Random Void User]

CudaText 1.221.5.2, linux-x86_64-gtk2, fpc 3.2.3

Reference:
https://github.com/Alexey-T/CudaText/issues/3800

I see this same warning dialog at random times while using CudaText GTK2. I doubt that it is specific to Void Linux. Void has both musl and glibc builds. I use the glibc build with Wayland/Sway. The GTK2 version of CudaText runs under XWayland.

[main Alexey]

hm, I don't have access violations with GTK2 version on Ubuntu (x11 or wayland). issue is Void Linux specific. not sure how to find the reason. I need to setup Void and install Lazarus there and debug there? I don't know when I can do it.

don't you want to setup Lazarus there and complile the Cud with debug information, and then run Cud under IDE and see that crash in IDE? I need the proper 'Call stack' from IDE when IDE shows the crash. menu item 'View / Debug windows / Call stack'.

you can setup the IDE quickly using fpcUpDeluxe tool: 2 clicks and FPC + IDE are installed after 20 minutes. https://github.com/LongDirtyAnimAlf/fpc ... e/releases

[main Alexey]

before using fpcUpDeluxe, let's try build x64/gtk2 with debug info. 57M sized binary.
https://github.com/Alexey-T/CudaText/di ... t-12344213

does it show more info on crash (in terminal)?

[Random Void User]

Thanks for those tools, I downloaded them. The error happens intermittently so I don't have a way to trigger it, but will report back when I get some info. Thanks!

[main Alexey]

Any update on this topic?

[main Alexey]

wait, I have good idea. I can compile the beta with debug info (it is much bigger) and now the app can log exceptions to the file cudatext.error (in home dir, if Linux).
you repeat the crash, you show me the crash log file.

[main Alexey]

here this beta:
https://github.com/Alexey-T/CudaText/di ... t-14367053