Hmm. I had the same thought, but when I get an error, I google it almost
reflexively. And when I did that, Google's AI overview suggested that it
was a message from the C++ runtime to connect a debugger.
I then "checked" that with ChatGPT and it also thinks this plausibly is
a message from the C++ runtime.
Anyway, the message to enable debugging isn't helpful in finding where
PSPP crashed.
-Alan
Google's AI overview says:
The message "(Press Retry to debug the application - JIT must be
enabled)" is a generic error from the Microsoft Visual C++ Runtime
Library. It appears when a program crashes due to a critical bug or an
"assertion failure". Despite what the error says, you do not need to
enable JIT (Just-In-Time) debugging.
ChatGPT says:
The message is associated with the Microsoft Visual C++ runtime, but JIT
debugging does NOT mean Java is involved.
There are two separate concepts:
*
Visual C++ runtime: The dialog can be generated by the C/C++ runtime
when an application triggers an assertion failure. Microsoft documents
this behavior, including the "Press Retry to debug" message.
*
JIT debugging: Just-In-Time debugging means launching or attaching a
debugger when a program encounters an error. It is not inherently a Java
feature. Visual Studio, for example, supports JIT debugging of native
C++ applications.
So, a C++ application can absolutely display this message without using
Java.
On 2026-09-17 09:49, Ben Pfaff wrote:
A JIT is usually for something like Java, but PSPP doesn't use a JIT or
Java or anything related, so I don't know why such a message would
appear.
On Thu, Sep 17, 2026 at 4:45 AM ftr <[email protected]> wrote:
Hi,
Yesterday and today, I got twice the same assertion failure with pspp
2.1.1-ge1319f.
At the end of the error message a cryptic message appears:
JIT must be enabled.
What does that mean, and how to enable it ?
Today, whatever I answer (abort ..) PSPP crashes and work is gone.
After the abort, several times the SAV file showed no file format
ending. But when I added .SAV to the file name, the data file
reappeared as a usable SAV file.
As a temporary solution, I now save the syntax file after every change
and save the data file, as well as the same file with the extension
'BAK' in the filename, every half hour.
You never know when a new assertion failure appears again, and why.
I am sorry, but currently I can't recommend PSPP for survey analysis.
I am really frustrated.
Regards
ftr
