I tried again, but opened a new session, not an existing session as before Ardour starts and seems to be Ok. After loading a plug in (that likely crashed the other session), GDB outputs shows “warning: executable loaded” and hangs. Hitting CTRL-C in the Ardour 8 GDB Terminal does not bring up the prompt, it just starts a new thread. I should be able to get to the GDB prompt from there, correct ?
I remeber seeing the GDB was updated in Ardour recently. Does this need a fix, or is something missing on my system ? I don’t know if there is useful information because there is a lot of this :
Installation error: gdb._execute_unwinders function is missing
Yes, that is a yes - it’s weird that system says it’s Haswell-ULT etc. instead of something like HD 4400 or HD 4600. This further implies that there is something wrong with integrated graphics driver.
Sorry, I confused the matter by using the Linux Driver name. The Windows driver name is Intelr(R) HD Graphics Family.
Also, I did not mention it here, but in the bug report that all of these plugins worked fine with Ardour 8.6 and 8.7, as well as other previous versions. I do not think that this is graphics related. Thank you for the suggestion.
That function is defined in Progam Files\Ardour8\gdb12\python3.10\gdb\__init__.py
and I don’t see any of these errors.
Perhaps the issue is that gdb picks up your local python3.12 install, instead of using the included python3.10 in Program Files\Ardour8\gdb12\python.exe ?
I’ve just set %PATH% to first look in the local folder:
Could an try if editing Program Files\Ardour8\debug.bat and adding the following helps?