WTF is a c++ execption

[skarmorystan505]

I was trying to run eternity engine, and I got the crash report I hopefully pasted below. Do any of y'all know what this is, and/or how to fix it? Any help is appreciated.

 

eternity caused a Microsoft C++ Exception (0xe06d7363)

Error occurred at 1/23/2024 20:02:10.
C:\Users\[redacted for personal privacy]\Downloads\games\Doom\eternity engine\eternity.exe, run by [redacted for personal privacy].
Operating system: 6.2.9200
4 processors, type 8664.
87% memory in use.
8077 MB physical memory.
972 MB physical memory free.
15245 MB page file.
5113 MB paging file free.
134217728 MB user address space.
134213500 MB user address space free.

===== [end of CRASHLOG.TXT] =====

[Dark Pulse]

It means that Eternity gave Micrsoft C++ a fabulous makeover, and it's now exceptional.

 

Okay, a non-shitpost answer: It's admittedly hard to tell exactly what. There's very little other information, and that error code seems to be a super-generic one.

 

Is there anything in the log before the exception?

[skarmorystan505]

Nope, I copied everything

[Dark Pulse]

Then my guess is that you're missing some kind of prerequisite it expects, or your system configuration is somehow not able to run it. Maybe your GPU drivers are out of date?

 

Alternatively, it could be the path name is too long and stuff is screwing up that way. Try moving it to somewhere with a shorter path (like in a folder directly under the root of C:.)

Edited January 24 by Dark Pulse

[Edward850]

Are you running the latest build as available in https://devbuilds.drdteam.org/eternity/ ? It is recommended you use x64 builds.

However it is worth nothing you are using Windows 8, not 8.1, but just plain 8 (either that or Windows Server 2012, but I doubt that), which is extra unsupported. While in theory it should still work, no one else can test on that platform.

[wesleyjohnson]

You do not say, but should:

What OS and version of OS  ( it reports 6.2 of something, What was Windows 6. I have a DOS 6.2, was it trying to run Eternity as a DOS program ?) ( I cannot see the Windows 8 that Edward mentions, he must recognize something not explicit).

What port of Eternity and its version that you were trying to run.

How was it installed, was everything installed into one directory, or was it installed to some specific directories  (I have had trouble with this step).

How did you start it, by command line, some desktop icon, or by a launcher.

Did it display ANYTHING that indicated that it started at all.  Most Doom will put up a title line first thing before they do anything else.  Are you seeing any Title line printout (and you may have to be in a console to see this which is why you should try this from a command line).

 

I have run several versions of Eternity in the past and do not remember ever encountering an Exception.  I program in C++, and Exceptions are usually something the programmer knew was not supposed to happen, so they used an Exception handling to cope.  Those kind of exceptions have names.  Those are usually reported as the name of the Exception that occurred.

System events are exceptions too, but those being known are usually reported accurately.

 

However, there is no telling with Windows and how they may have changed normal error reporting.

 

I have had trouble installing Eternity lately (on Linux), and now have a new system and have not gotten it installed there either.

It wants files that I cannot figure where they are supposed to come from.

On :Linux, it just says that these files cannot be found.  It does not report those as Exceptions, and I do not know how it could be that different on Windows.

 

That leaves something extraordinary.

You don't say if Eternity was ever run before, or if this is a new install.  I think everyone is going to assume a new install.

 

Possibilities:

  Trying to run a modern binary on an OS version that is too old for it.

  Check your compatibility switches on any of those execution indirections (Do not run Eternity as a DOS program, nor as a Win3.1 program, unless that is exactly what binary you have, and I don't think Eternity has got one for those).

  A corrupted binary that fails, try a different download, and different version

  A Windows binary compiled for a different processor, or different hardware, or different OS.

  You are trying to execute something that is not a binary, as if it was a binary, and windows is letting you (which it generally did not allow, but who knows these days).

  Some system resource that Eternity assumes, is not present, such as OpenGL.

  A corrupted resource file, that fails upon reading due to not being in the needed format.  A low level file read failure errors differently than a read error by the program.  Again, this is OS  dependent, but even more it is dependent upon what low level resource it was trying to access.

I do not know if Eternity tries to set any config, and what happens when it is corrupted.

Some old config can hang around for years.

  Mis-configured memory (that is a huge MB of user memory being reported (134 TB), is that really what you have).

  If it was as simple as a missing library, it would report it differently and more explicitly.

 

Try running it on a command line, so you can use the command line switches and see the standard messages during startup.

Put a copy of a simple Doom WAD in the directory with the Eternity binary.

I know that most Windows users do not know how to run command line, but for this it is the best way to diagnose the problem.

Because I don't have Eternity setup here (especially not setup like you have), I cannot give you an example.

Can someone give an example command line for this Eternity version ??

 

I run Linux, but I also have an XP.  Trying to diagnose this Windows 6 problem, by people who now run Windows 11, is probably not going to be ideal either.  I have an XP here to compare to, but do not remember trying to install Eternity on it.  I have not ever seen something like that on the XP, not at all after developing DoomLegacy on it.  DoomLegacy and Eternity are similar enough that we can at least borrow some code.

 

Edited January 29 by wesleyjohnson

[Edward850]

wesleyjohnson, I mean this in the nicest possible way, but you have not contributed anything helpful to the topic at hand. You don't seem to understand Windows at all, and this is not an area you can help with, it appears. You mostly appear to have incredibly old knowledge that no longer applies.

[wesleyjohnson]

The question has been here a week, and I have not seen any better info to help.  It also appears to be an older OS, like that XP I use for the DoomLegacy windows binary.

I have spent that last two weeks trying to track down C++ exceptions being thrown by code I did not write.

Why not fill in some of the information holes, if you have more explicit information.

 

 

Edited January 29 by wesleyjohnson

[Edward850]

12 minutes ago, wesleyjohnson said:

The question has been here a week, and I have not seen any better info to help.  It also appears to be an older OS.

 

I asked if they are using the latest version, i believe they are not. They have not responded so no additional information could be given. Nothing you have contributed has any relevance here, and you don't even understand the crash given your lack of debugging tools for Eternity.

I also already explained what OS they have, which you would know if you actually read my post before instead of contributing your word salad.

Edited January 29 by Edward850

[wesleyjohnson]

Are you going to point him at some of those debugging tools for Eternity.  I could use something to figure out why I cannot get Eternity to install cleanly on Linux.

I debug other people's code about 10 hours a day, so I am familiar with C++ exceptions.  Unless Eternity or this Windows is much different than the debugging I do every day, this user should not be seeing C++ exceptions.  Please fill in what situations specific for Eternity and this version of windows would produce such a C++ exception.

Is there something about that error message that says it is Windows 8 ?, if so then can you provide some information that could help.

Does that version 6.2 mean DOS 6.2?  Is that normal for this version of Windows to report its DOS version.  That is where you should be able to follow up on this.

Please go ahead and follow up, I think there are many more suggestions that could be provided to this user than what he got.

 

 

Edited January 29 by wesleyjohnson

[Edward850]

11 minutes ago, wesleyjohnson said:

Are you going to point him at some of those debugging tools for Eternity.

I am going to wait for them to verify they are using the latest build. Only then does it make sense to start isolating where their callstack be at (and notably, why they seem to be missing one, which I believe is a symptom of using older builds).

11 minutes ago, wesleyjohnson said:

I debug other people's code about 10 hours a day, so I am familiar with C++ exceptions.

The C++ exception is arbitrary, it does not refer to any one specific problem and you seem to be jumping to weird conclusions.

11 minutes ago, wesleyjohnson said:

Is there something about that error message that says it is Windows 8 ?, if so then can you provide some information that could help.

Literally in their initial post, that is what Operating system: 6.2.9200 means. Windows 8 is version 6.2.9200.

11 minutes ago, wesleyjohnson said:

Does that version 6.2 mean DOS 6.2? 

In no possible way does this mean DOS. You are so in the past it's not funny, it's actually annoying. For precisely this unnecessary conversation.

11 minutes ago, wesleyjohnson said:

Please go ahead and follow up, I think there is much more suggestions that could be provided to this user than what he got.

I would actually prefer it if you would stop trying to help, all you have done is make a mess.

Edited January 29 by Edward850

[act]

no idea m8