Page 1 of 1
GTK2 Access Violation Still Happens
Posted: 27.02.2025 19:14
by 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.
Re: GTK2 Access Violation Still Happens
Posted: 27.02.2025 20:54
by 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
Re: GTK2 Access Violation Still Happens
Posted: 27.02.2025 21:10
by 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)?
Re: GTK2 Access Violation Still Happens
Posted: 28.02.2025 19:13
by 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!
Re: GTK2 Access Violation Still Happens
Posted: 15.03.2025 09:14
by main Alexey
Any update on this topic?