Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Bryan See on December 08, 2016, 08:42:18 am

Title: Unable to start
Post by: Bryan See on December 08, 2016, 08:42:18 am
Recently, I've got a nightly build and when I tried to run FRED2, it gets a runtime error message. Running the debug version gets the same thing.

As for the main FS2Open executable, I got a message saying:

Code: [Select]
Error: Caught std::exception in main(): 'Failed to open file'!
File: freespace.cpp
Line: 8128

Running the debug version, I get the error message saying I don't have admin privileges to run that program.

Is there some problems in these builds that cause all of these?

[attachment deleted by admin]
Title: Re: Unable to start
Post by: The E on December 08, 2016, 09:02:21 am
Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

Try starting the debug build with admin priviledges.
Title: Re: Unable to start
Post by: Bryan See on December 08, 2016, 09:23:56 am
Still cannot start debug builds to obtain the fs2_open.log file. I'm getting a "The stub received bad data" error message or some permissions error message.
Title: Re: Unable to start
Post by: m!m on December 08, 2016, 10:51:42 am
The error is probably caused by an asset problem (a file is either missing or is empty) but it shouldn't crash FSO. I have submitted a pull request which should fix all the possible locations where this could have happened: https://github.com/scp-fs2open/fs2open.github.com/pull/1086
Title: Re: Unable to start
Post by: Bryan See on December 09, 2016, 09:58:54 am
I think this should apply to empty table files, especially future additions.
Title: Re: Unable to start
Post by: AdmiralRalwood on December 09, 2016, 10:02:51 am
I think this should apply to empty table files, especially future additions.
Why would FSO possibly be unable to open an empty file? And why would we want future new table files to error if they couldn't be found? That would just make retail data generate errors, which violates rule #1.
Title: Re: Unable to start
Post by: Bryan See on December 10, 2016, 10:19:15 am
I think this should apply to empty table files, especially future additions.
Why would FSO possibly be unable to open an empty file? And why would we want future new table files to error if they couldn't be found? That would just make retail data generate errors, which violates rule #1.
As m!m said, it's because of an asset problem (a file is either missing or is empty). It's going to be fixed soon.

EDIT (UPDATE):
I'm getting an error message saying "The instruction at 0x00007FFF2E2F00E8 referenced memory at 0x00007FFF2E2F00E8. The memory could not be written." when attempting to run non-debug FRED2Open and debug FS2Open. Also, I'm getting a permissions error message on the non-debug FS2Open executable. The debug version of FRED2Open however, was started without a problem.