[Github-comments] [geany/geany] Geany 1.33 AutoSave FilesOpenList, using Debian Buster 10 in Oracle VirtualBox inside Windows 10 PC (Issue #3502)

2023-05-15 Thread SymbReprUnlim via Github-comments
Issues/Statement of Issues to be hopefully Solved: 1a) Linux Terminal commands sudo apt update and sudo apt full-upgrade never update Geany 1.33 to its current version of 1.38. Thus Geany 1.33 remains apparently the "latest available" version of Geany within a Windows PC running Oracle Virtual

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2019-01-25 Thread Matthew Brush
I guess a debug build of GTK+/GDK/GLib would be needed to see what's going on. It might be possible to get packages for those symbols/debug-builds using msys2 package manager to find them for the same version as used in the debug build of Geany provided in #795. -- You are receiving this

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2019-01-25 Thread elextr
@NTMan yeah, all it shows is that its in GTK, the only Geany code was the call to `gtk_main()` at libmain.c:1250. Unfortunately GTK apps are all callbacks, so once they have finished and returned to GTK there is no record of what the Geany code did. Maybe GTK symbols might help, but I suspect

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2019-01-25 Thread Mikhail
with debug symbols from https://github.com/geany/geany/issues/795 it looks like: ``` Program received signal SIGSEGV, Segmentation fault. 0x0074e3a9 in ?? () from C:\Program Files (x86)\Geany\bin\libgdk-win32-2.0-0.dll (gdb) thread apply all bt full Thread 8188 (Thread 13080.0x2d28): #0

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-12-04 Thread elextr
@NTMan thanks, unfortunately it shows that its in GTK, the crash is in thread 1 according to the address of the segv, and thread 1 shows no Geany code except the startup that calls GTK. Since there is no Geany code in the traceback which might have provided some idea what was happening, really

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-12-04 Thread Mikhail
@eht16 ``` Program received signal SIGSEGV, Segmentation fault. 0x6c55e3a9 in ?? () from C:\Program Files (x86)\Geany\bin\libgdk-win32-2.0-0.dll (gdb) thread apply all bt full Thread 809 (Thread 20896.0x4cfc): #0 0x77011f76 in ntdll!ZwWaitForWorkViaWorkerFactory () from

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-12-02 Thread Enrico Tröger
@elextr We don't have any debug builds or seperate symbols for download. @NTMan even without debug symbols, a backtrace might help to. If possible, please start Geany in gdb and "wait" for the crash. I know this is supoptimal, especially regarding performance. But no better idea so far. --

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-11-28 Thread elextr
@NTMan oh, I thought we had a download with symbols, maybe I'm mistaken, @eht16 ? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2000#issuecomment-442727183

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-11-28 Thread Mikhail
> Geany is built with the GCC compiler, it does not provide the proprietary > debug symbols needed to use Microsoft debug tools. (see > [here](https://stackoverflow.com/questions/44456068/how-to-compile-c-program-in-gcc-to-enable-debug-in-windbg/44456383#44456383)) > > Instead you should run

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-11-28 Thread elextr
Geany is built with the GCC compiler, it does not provide the proprietary debug symbols needed to use Microsoft debug tools. (see [here](https://stackoverflow.com/questions/44456068/how-to-compile-c-program-in-gcc-to-enable-debug-in-windbg/44456383#44456383)) Instead you should run Geany under

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-11-28 Thread Mikhail
> What exactly means "nearly every month"? > Is it at the first of a month or at the last day? It means that Geany usually crashes one time in month. > What do you do when it crashes? Nothing unusual. I am just edit code. > Do you keep Geany running 24/7? Yes. > What are the `.dmp` files you

Re: [Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-11-28 Thread Enrico Tröger
What exactly means "nearly every month"? Is it at the first of a month or at the last day? What do you do when it crashes? Do you keep Geany running 24/7? What are the `.dmp` files you posted, how to use it? -- You are receiving this because you are subscribed to this thread. Reply to this

[Github-comments] [geany/geany] Geany 1.33 for Windows nearly every month crashes. (#2000)

2018-11-28 Thread Mikhail
Geany 1.33 for Windows nearly every month crashed. Crash dumps you can find here: https://mega.nz/#F!ns0xRYYA!6VuD1TZX5Cr5HGwYYuHN5A -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2000

[Github-comments] [geany/geany] Geany 1.33

2018-02-25 Thread Enrico Tröger
## Bug fixes * Fix the symbols tree hierarchy when several tags have the same name ([PR#1598](https://github.com/geany/geany/pull/1598)). ## Interface * Add a tooltip showing the full path on menu items representing documents ([PR#1706](https://github.com/geany/geany/pull/1706)). * Add a note