Aergis
|
|
Posted on: July 18, 2012, 07:31:10 pm |
|
|
Joined: Jul 2012
Posts: 13
|
I just downloaded ENIGMA using the instructions outlined here: http://enigma-dev.org/download.htm I also tried both sample games and when I click ENIGMA->Run the console opens and finishes, the ENIGMA Shell pops up, greys out, then a Windows crash error shows up saying "emg.tmp has stopped working" "Close Program", then when I click "Close Program" the console says "Game returned 255". I'm using Windows 7 64-bit
|
|
« Last Edit: July 19, 2012, 05:04:49 pm by Aergis »
|
Logged
|
|
|
|
polygone
|
|
Reply #1 Posted on: July 18, 2012, 07:46:32 pm |
|
|
Location: England Joined: Mar 2009
Posts: 794
|
What sample game did you try? I'm not sure the ones on the wiki are still working that page probably hasn't been updated in a while. Try this game instead: http://enigma-dev.org/edc/games.php?game=4
|
|
|
Logged
|
I honestly don't know wtf I'm talking about but hopefully I can muddle my way through.
|
|
|
|
polygone
|
|
Reply #3 Posted on: July 18, 2012, 07:58:04 pm |
|
|
Location: England Joined: Mar 2009
Posts: 794
|
Hmm unfortunately that makes it extremely difficult to debug since there is no error for us to go on. Can you just check to see if a completely blank new game does the same thing as well please?
If so I think Josh needs to test things on newer Windows systems a little. The problem is no one in the dev team uses Windows 7 so incompatibilities with it are more likely to go unnoticed.
|
|
|
Logged
|
I honestly don't know wtf I'm talking about but hopefully I can muddle my way through.
|
|
|
|
polygone
|
|
Reply #5 Posted on: July 18, 2012, 08:13:29 pm |
|
|
Location: England Joined: Mar 2009
Posts: 794
|
Yeah unfortunately that error doesn't tell us anything at all because there doesn't appear to be anything wrong with ENIGMA; the problem is being caused by some incompatibility with your system. Like I said not a lot of testing hasn't been done on Windows 7 so there might lay some unknown incompatibilities there or it could just be something specific about your system. Hopefully Josh will be be back on soon, its probably best wait to see what he suggests.
|
|
|
Logged
|
I honestly don't know wtf I'm talking about but hopefully I can muddle my way through.
|
|
|
polygone
|
|
Reply #6 Posted on: July 18, 2012, 09:27:15 pm |
|
|
Location: England Joined: Mar 2009
Posts: 794
|
Josh has suggested trying to run a game build on my system to see if it will run on yours. So if you could see if this please runs it would be useful: https://www.box.com/files#/files/0/f/72770310/1/f_2666779757Thanks.
|
|
|
Logged
|
I honestly don't know wtf I'm talking about but hopefully I can muddle my way through.
|
|
|
|
polygone
|
|
Reply #8 Posted on: July 18, 2012, 09:43:11 pm |
|
|
Location: England Joined: Mar 2009
Posts: 794
|
Sorry that's my bad, didn't give the correct share link: https://www.box.com/s/c8bb78593a08275643acI blame the fact that it's nearly 4am <_<
|
|
|
Logged
|
I honestly don't know wtf I'm talking about but hopefully I can muddle my way through.
|
|
|
|
Josh @ Dreamland
|
|
Reply #10 Posted on: July 18, 2012, 09:59:19 pm |
|
|
Prince of all Goldfish
Location: Pittsburgh, PA, USA Joined: Feb 2008
Posts: 2950
|
You are running Windows 7, 64bit, I presume? Is there anything notable about your Windows environment? Also, it might help if we knew what graphics card you used, and possibly some info from running dxdiag. Basically, computer specs might help.
Better yet, it would help if you could run a debug version of the program through GDB for us, so we have an idea of what is failing. Have you ever used GDB before?
|
|
|
Logged
|
"That is the single most cryptic piece of code I have ever seen." -Master PobbleWobble "I disapprove of what you say, but I will defend to the death your right to say it." -Evelyn Beatrice Hall, Friends of Voltaire
|
|
|
Aergis
|
|
Reply #11 Posted on: July 18, 2012, 10:13:44 pm |
|
|
Joined: Jul 2012
Posts: 13
|
You are running Windows 7, 64bit, I presume? Is there anything notable about your Windows environment? Also, it might help if we knew what graphics card you used, and possibly some info from running dxdiag. Basically, computer specs might help. here are the specs from dxdiag: Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Processor: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz (8 CPUs), ~1.7GHz Memory: 6144MB RAM Page file: 3960MB used, 8248MB available DirectX Version: DirectX 11 Display Device Name: ATI Mobility Radeon HD 5870 Display Device Approx. Total Memory: 3790 MB Better yet, it would help if you could run a debug version of the program through GDB for us, so we have an idea of what is failing. Have you ever used GDB before? do you mean click Enigma->Debug? Idk what GDB is.
|
|
|
Logged
|
|
|
|
Josh @ Dreamland
|
|
Reply #12 Posted on: July 18, 2012, 10:24:01 pm |
|
|
Prince of all Goldfish
Location: Pittsburgh, PA, USA Joined: Feb 2008
Posts: 2950
|
Okay, from your specs, you should have absolutely everything you need to run ENIGMA successfully. Anyway, GDB is the GNU debugger. It's proficient at finding the point at which programs die. Unfortunately, you have to know a few commands to be able to do it. I'll try to give the step-by-step, but it'd be easier to walk you through over IRC. - First, download this version of Verlet, compiled with debugging symbols: https://www.box.com/s/fcf24b61d614b1194c54. You can technically build your own by selecting Debug from the ENIGMA menu and copying the executable out of the temporary files.
- Next, open an msys bash shell. There should be a program under C:\MinGW\MSys\1.0\bin\ called "bash.exe" or similar. You may need to open it from a terminal.
- Once the bash shell is open, input [snip]gdb "Verlet (Debug).exe"[/snip] and press Enter. You may need to replace "Verlet (Debug).exe" with the full path to the program. A line starting with (gdb) should display.
- Type [snip]run[/snip] and press enter. The program should attempt to start.
- From there, GDB will print the error that occurred, probably SIGSEGV (segmentation fault). If it does, type [snip]backtrace[/snip], or "bt" for short.
- GDB should then output a list of functions on the call stack before the program exploded. Copy the contents of the terminal, and paste them to us (either here or on Pastebin.
If you have trouble copying text from the terminal, try right clicking the title bar and going to Edit->Select All/Copy.
|
|
« Last Edit: July 18, 2012, 10:26:10 pm by Josh @ Dreamland »
|
Logged
|
"That is the single most cryptic piece of code I have ever seen." -Master PobbleWobble "I disapprove of what you say, but I will defend to the death your right to say it." -Evelyn Beatrice Hall, Friends of Voltaire
|
|
|
|
Aergis
|
|
Reply #14 Posted on: July 18, 2012, 11:49:45 pm |
|
|
Joined: Jul 2012
Posts: 13
|
here's the bt
bash.exe"-3.1$ cd /c/MinGW/bin bash.exe"-3.1$ gdb "Velvet (Debug).exe" GNU gdb (GDB) 7.4 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-mingw32". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Velvet (Debug).exe: No such file or directory. (gdb) run Starting program: No executable specified, use `target exec'. (gdb) file No executable file now. No symbol file now. (gdb) cd /c/MinGW/msys/1.0/bin/ /c/MinGW/msys/1.0/bin/: No such file or directory. (gdb) file No executable file now. No symbol file now. (gdb) file /c/MinGW/mysys/1.0/bin/"Velvet (Debug).exe" /c/MinGW/mysys/1.0/bin/Velvet (Debug).exe: No such file or directory. (gdb) file /c/MinGW/mysys/1.0/bin/ /c/MinGW/mysys/1.0/bin/: No such file or directory. (gdb) "Velvet (Debug).exe" Undefined command: "". Try "help". (gdb) Velvet(Debug).exe Undefined command: "Velvet". Try "help". (gdb) VelvetDebug.exe Undefined command: "VelvetDebug". Try "help". (gdb) file VelvetDebug VelvetDebug: No such file or directory. (gdb) file VelvetDebug.exe VelvetDebug.exe: No such file or directory. (gdb) file No executable file now. No symbol file now. (gdb) file "C:\MinGW\mysys\1.0\bin\Verlet (Debug).exe" C:MinGWmysys1.0binVerlet (Debug).exe: No such file or directory. (gdb) q bash.exe"-3.1$ gdb "c/MinGW/mysys/1.0/bin/Verlet (Debug).exe" GNU gdb (GDB) 7.4 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-mingw32". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... c/MinGW/mysys/1.0/bin/Verlet (Debug).exe: No such file or directory. (gdb) q bash.exe"-3.1$ gdb "c:/MinGW/mysys/1.0/bin/Verlet (Debug).exe" GNU gdb (GDB) 7.4 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-mingw32". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... c:/MinGW/mysys/1.0/bin/Verlet (Debug).exe: No such file or directory. (gdb) q bash.exe"-3.1$ gdb "c:/MinGW/bin/Verlet (Debug).exe" GNU gdb (GDB) 7.4 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-mingw32". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from c:\MinGW\bin\Verlet (Debug).exe...done. (gdb) run Starting program: c:\MinGW\bin\Verlet (Debug).exe [New Thread 17304.0x5b44]
Program received signal SIGSEGV, Segmentation fault. 0x6903b212 in atioglxx!DrvShareLists () from C:\Windows\SysWOW64\atioglxx.dll (gdb) bt #0 0x6903b212 in atioglxx!DrvShareLists () from C:\Windows\SysWOW64\atioglxx.dll #1 0x00005b44 in ?? () #2 0x6903a73c in atioglxx!DrvSwapLayerBuffers () from C:\Windows\SysWOW64\atioglxx.dll #3 0x76551222 in KERNEL32!GetPrivateProfileStructA () from C:\Windows\syswow64\kernel32.dll #4 0x5fffaf0b in wglSwapMultipleBuffers () from C:\Windows\SysWOW64\opengl32.dll #5 0x5fffb0f3 in wglSwapMultipleBuffers () from C:\Windows\SysWOW64\opengl32.dll #6 0x5fffb1a9 in wglSwapMultipleBuffers () from C:\Windows\SysWOW64\opengl32.dll #7 0x5fffc6a4 in wglGetProcAddress () from C:\Windows\SysWOW64\opengl32.dll #8 0x60005658 in wglGetPixelFormat () from C:\Windows\SysWOW64\opengl32.dll #9 0x60005dd4 in wglDescribePixelFormat () from C:\Windows\SysWOW64\opengl32.dll #10 0x60006559 in wglChoosePixelFormat () from C:\Windows\SysWOW64\opengl32.dll #11 0x768458b7 in GdiEntry12 () from C:\Windows\syswow64\gdi32.dll #12 0x2d0123f1 in ?? () warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
#13 0x00000001 in ?? () warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x9 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x9 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x9 in read in psymtab, but not in symtab.)
#14 0x0000000a in ?? () warning: (Internal error: pc 0x9 in read in psymtab, but not in symtab.)
#15 0x5ffc0000 in ?? () #16 0x00422c60 in enigma::EnableDrawing (hRC=0x28fe78) at Platforms/Win32/WINDOWSstd.cpp:62 #17 0x00422a53 in WinMain@16 (hInstance=0x400000, hPrevInstance=0x0, lpCmdLine=0xfe38d2 "", iCmdShow=10) at Platforms/Win32/WINDOWSmain.cpp:140 #18 0x0051823e in main ( argc=<error reading variable: Cannot access memory at address 0x3>, argv=<error reading variable: Cannot access memory at address 0x7>, __p__environ=<error reading variable: Cannot access memory at address 0xb>) at ../mingw/main.c:73 (gdb)
|
|
|
Logged
|
|
|
|
|