Hi Michael, thank you very much for your time! One question - do you think it would be any different if I moved to Linux?
And thanks to everyone that works on Lilypond, what an incredible product! -----Original Message----- From: Michael Käppler <[email protected]> Sent: Tuesday, May 19, 2026 1:31 AM To: [email protected]; 'Karlin High' <[email protected]>; 'Jonas Hahnfeld' <[email protected]> Cc: 'bug-lilypond' <[email protected]> Subject: Re: v2.26.0 fails to start with return code -1073741569 (0xC00000FD) Hi Steve, sorry for not replying earlier. Great that you managed do get a backtrace. The backtrace points to a problem within Guile, the Scheme interpreter Lilypond is built upon. We currently do not release Lilypond for Windows ARM, because setting up the compilation environment is far from being trivial and the Windows support in Guile (speaking about x86_64) is buggy and fixes get upstreamed very slowly. AFAICT, no one is working on Windows ARM support for Guile at the moment. That said, x86_64 Guile should run in the emulation layer and it should be possible to find out why it does not. Unfortunately I currently have very little time to help you. What I would like to do is sending you a self-contained Guile executable compiled against the newer Windows C runtime (UCRT) to see if the problem persists and/or verify that the problem is not a subtle issue within the Lilypond-Guile interface. Not sure when I will manage to do this, though. Michael Am 19.05.26 um 00:45 schrieb [email protected]: > Hello, > > Did the WinDbg output help? Is there anything else I can provide? > > I noticed that 2.27 dev was released and saw there were ARM versions > listed for MacOS but none for Windows. ☹ > > Thanks, > Steve > > -----Original Message----- > From: [email protected] <[email protected]> > Sent: Tuesday, April 28, 2026 2:41 AM > To: 'Michael Käppler' <[email protected]>; 'Karlin High' > <[email protected]>; 'Jonas Hahnfeld' <[email protected]> > Cc: 'bug-lilypond' <[email protected]> > Subject: RE: v2.26.0 fails to start with return code -1073741569 > (0xC00000FD) > > I'm not very familiar with WinDbg but I installed it from Microsoft Store and > I think I managed to run lilypond with command line arguments to process > testscore.ly. > > I tried to disable the JIT compilation as well, here's what I tried - > >> set GUILE_JIT_THRESHOLD=-1 >> C:\Users\steve\AppData\Local\Microsoft\WindowsApps\WinDbgX.exe -o -g >> -G >> "C:\Users\steve\AppData\Local\frescobaldi\frescobaldi\lilypond-binari >> e s\lilypond-2.26.0\bin\lilypond.exe" -o testscore.pdf testscore.ly > WinDbg output attached. > > -----Original Message----- > From: Michael Käppler <[email protected]> > Sent: Monday, April 27, 2026 3:14 AM > To: [email protected]; 'Karlin High' <[email protected]>; > 'Jonas Hahnfeld' <[email protected]> > Cc: 'bug-lilypond' <[email protected]> > Subject: Re: v2.26.0 fails to start with return code -1073741569 > (0xC00000FD) > > Thanks, > your attached file shows exception code 0xC00000FF -> > 'STATUS_BAD_FUNCTION_TABLE' > which means 'A malformed function table was encountered during an unwind > operation.' > [Source: > https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref > /596a1078-e883-4972-9bbc-49e60bebca55] > > Can you try to run lilypond through WinDbg? > https://aka.ms/windbg/download > > Michael > > Am 27.04.26 um 06:04 schrieb [email protected]: >> There is not any popups or anything other than that return code. I’ve >> reviewed the entries in Event Viewer several times while testing this but >> nothing ever showed there. >> >> >> >> The only thing I can ever find is in >> C:\ProgramData\Microsoft\Windows\WER\ReportArchive where there are >> many folders with names - >> >> >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 012e335f-a8ad-4555-8fd6-ad65457285ba >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 09c24a07-d3ea-4713-aca9-0fac4b48e20b >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 1cb7287c-6850-4239-bf0a-ddf7bece9c77 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 1da753e8-7ffa-471f-a8ed-227f27266f5f >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 22842cbd-7966-4b98-9525-73895ea4d17b >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 34bdfc75-de73-4848-9fff-e22be4724324 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 34f7606a-3a05-4d3d-8245-129462c90ff2 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 42da5237-9a10-4a27-9c49-345f4ea78dcf >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 50b44121-9e66-4f7d-a557-f1739feeebf0 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 59a68c59-1f93-4f17-99cf-044bbf43b47c >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 5dae2d55-ac8e-4db2-a663-ca47b6bd19e7 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 60686176-3756-42e1-9572-b3630eba2df7 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 672fd283-dcf1-48dc-9f2f-b29621c720d2 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 67e145ad-6fee-4fcb-a419-479a66791f73 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 803a293e-8d5d-4944-901e-9e162c2915f5 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> 9c9aafe9-988c-46ee-a2c2-8aa94b8a6f0d >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> a5350633-a0ef-4cf9-83b1-fddd4763ec9a >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> c1f17038-9892-4a7d-b15f-89c9ca947532 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> cac4cf8d-ca83-4acd-b8e1-54b5a5b1fb92 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> ccabf9b3-4282-4a2d-bdd2-21dee69d8b79 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> e4fc6981-53a5-4b7b-ad58-49239d850b9b >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> ee8736de-136b-4d36-8240-0a1b9cc33de1 >> >> AppCrash_lilypond.exe_fd37ad8d12639d5b538b952110a87f70bf2de6_74c2b572 >> _ >> fbf67d96-0e23-4ddd-8741-ff86a40fad5d >> >> and inside each folder there is one file, Report.wer (most recent attached). >> >> >> >> Thanks, >> >> Steve >> >> >> >> From: Karlin High <[email protected]> >> Sent: Sunday, April 26, 2026 7:01 AM >> To: Jonas Hahnfeld <[email protected]> >> Cc: [email protected]; bug-lilypond <[email protected]> >> Subject: Re: v2.26.0 fails to start with return code -1073741569 >> (0xC00000FD) >> >> >> >> On Sun, Apr 26, 2026, 2:47 AM Jonas Hahnfeld via bug-lilypond >> <[email protected] <mailto:[email protected]> > wrote: >> >> When it crashes, do you get a popup that would allow you to get a >> stack trace / crash report? These might just be hexadecimal numbers >> (0x...) >> >> >> >> And if there is no popup, check Windows Event Viewer. There are separate >> logs for System and Application, either could be interesting. >> >> -- >> >> Karlin High >> >> Missouri, USA >>
