-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APPCRASH: Segmentation Fault #2
Comments
Thanks for the report. If you send us your source code (or just the |
Multiple attempts to mail you the source and object files failed. As a workaround I have uploaded the files to Google Drive and sharing the link. This is the link - https://drive.google.com/file/d/1l97kDA6jtxpR7JKq8hcRsabyiHGcEDeT/view?usp=drivesdk Waiting for your reply and a solution. |
I tried building main.obj with Crinkler 2.3 using the arguments in your initial post and it seems to link, compress and run just fine here. I wonder if the problem might stem from you using a different environment with different libs that causes Crinkler to produce an invalid executable. I'm running Crinkler from the VS2019 command prompt ("x86 Native Tools Command Prompt for VS 2019" in the start menu). What does your environment look like? Alternatively, Crinkler executables might just not work on your machine for some reason. We have previously seen 3rd party software trying to scan Crinkler executables, getting confused and ultimately causing a crash. Can you try if the executable I built runs on our machine? |
I ran the |
That is interesting. As far as we know, Crinkler should still be compatible with Windows 7, although I don't think we have ever tested the Ultimate Edition specifically. It might also be related to 3rd party software. We have previously seen graphics drivers scanning executables to detect which game-specific optimizations to apply. Which graphics card / driver are you using? Do you have any unusual programs installed? Anti-virus software, etc? Most programs won't start automatically when you start windows in safe mode. Can you try running out.exe in safe mode to help narrow it down? |
I ran the executable
But when I ran it in normal mode, it gave this error message
|
Those crash summaries give a useful hint about what goes on. In particular, The Crinkler import code crashes while reading the name of one of the functions in one of the imported DLLs (to compute a hash of the name). This would seem to indicate that one of those DLLs is shaped in an untraditional way that the Crinkler import code does not understand. Can you make available the |
Okay. I'll make an archive and upload it on drive and provide the link. Thanks for your reply. |
On a different note, I am on a 32 bit windows system. I have system32 folder but no syswow64 |
Interesting. That could very well be related to the error. I think it's been quite a while since we last tested on a 32-bit Windows.
|
Thank you so much for your quick reply. I have included all the dlls you asked and also the source code and build script of my project. Drive link: |
Did you link that executable with Since the program also crashes with |
I took a look at the DLL files in your archive, and I can't see anything wrong with them. It's probably some weirdnees with your system. Can you run other Crinkler-compressed executables, i.e. any 4k intro? |
I was trying to compress a win32 application with crinkler. I ran the following commands -
cl /c /O1 /GS- /Oi- /Gs9999 main.c
crinkler /TINYHEADER /SUBSYSTEM:WINDOWS main.obj kernel32.lib user32.lib gdi32.lib
It generates
out.exe
. But when I run the executable, it crashes with exception codec0000005
. I ran the same executable in git bash where it showed segmentation fault. I googled the problem and found that it was trying to access some inaccessible memory region.The program runs just fine when linked by
link.exe
The text was updated successfully, but these errors were encountered: