Re: exit code running out the shell question
[email protected] (ToddAndMargo via perl6-users) Wed, 5 Nov 2025 21:40:51 -0800
| Newsgroups | perl.perl6.users |
|---|---|
| Message-ID | <[email protected]> |
On 11/5/25 9:32 PM, ToddAndMargo via perl6-users wrote: > Hi All, > > Why would a Raku program return an exit code of > -1073741510 (3221225786)? > > Yours in Confusion, > -T This is happening to me in Windows 10 Search.brave.com's AI states this: https://search.brave.com/search?q=why+would+a+raku+return+an+exit+code+of+-1073741510&spellcheck=0&source=alteredQuery&summary=1&conversation=d94c64bece8d47d076d8ea The exit code -1073741510 (0xc000013a) is a Windows-specific error code that indicates an application was terminated abruptly during a logoff or shutdown sequence. This error is not directly related to Raku itself but can occur if a Raku program is running as part of a larger application or service that is terminated unexpectedly, such as when the system shuts down too quickly for the process to exit gracefully. The error typically arises when the operating system does not allow sufficient time for the application to close properly, which can happen during a Windows logoff or shutdown. When I run my program manually, it exits perfectly. Since this runs unattended, how it the world do I trace this down? Log every subroutine that is called? Is there a tracing module that will do this for me? Yours in Confusion, -T