Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Volatar

Pages: [1]
1
General / Re: Welp, this is a good start: "Run-Time Check Failure #2"
« on: November 17, 2014, 10:34:11 am »
Ah ha! Moments after posting I figured out the problem. But I am not going to be that guy and just say "I fixed it" and move on.

What did I do wrong?

Well, when I compiled, I then moved the things I needed out of the various... stuff created by cmake (the .libs and .dll's) to my project files. However, I also needed the includes, so I simply copied those over to my project folder and moved on.

What I did wrong was I copied the wrong includes folder. I copied the one from the 2.1 stable branch I had open to check if I was getting the right things I needed. I should have copied them from the source code I had downloaded, which is more up to date than the 2.1 stable it seems, even though they are next to each other on the download page.

Hope this helps someone in the future. :)

2
General / Welp, this is a good start: "Run-Time Check Failure #2"
« on: November 17, 2014, 10:21:55 am »
"Run-Time Check Failure #2 - Stack around the variable 'window' was corrupted." is the full error message. Couldn't fit it into the title. Don't think I need to from my Googling. Quite a few instances of the same error pop up.

When does this error occur and with what code?

Code is right from the test at the end of the Visual Studio tutorial:

(click to show/hide)

I get the error when I hit the X to close the little window. First time it came up I hit continue instead of break and I can't end the program anymore xD. Had to reboot to fix that. No big deal. Hitting break allows me to kill it thankfully.

Now here is where it gets interesting I think: two solutions come up in my Googling:

Either A: I am using a version of the library compiled for a different compiler.
or B: I have mixed up my linking between debug and release.

A: Yes, I am running Visual Studio 2013 (update 4). However, I compiled the libraries myself mere minutes before, so that should not be the problem.
B: I keep checking *checks again*... yep, I got the linking right. -d to debug, no -d to release.

I will note that release builds do not throw this error message, but that's because the release build lacks the error handling the debug one does I think. I could be wrong though.

So, any thoughts? Need any more information? I am happy to provide.


3
General / Crash at app run
« on: October 20, 2010, 12:37:25 am »
Thank you so much!

4
General / Crash at app run
« on: October 18, 2010, 10:22:32 pm »
I get the same error when trying to compile the same code on my W7 (32-bit) laptop with VS2010 Express (professional on my desktop) I get the same error.

Do you think you could zip up and post your already working copy of SFML so I could see if it works PeterWelzien? Batch build fails for me. I would be extremely greatful  :)

5
General / Crash at app run
« on: October 13, 2010, 01:35:12 pm »
At what point? When I copy them over to the project files?

I don't actually have any other versions on my machine. I deleted all the other ones to be sure. However, it is possible that the ones I have are wrong.

How do I check them to see if they are correct?

6
General / Crash at app run
« on: October 13, 2010, 12:18:33 pm »
Yep. Thats exactly what we tried last.

7
General / Crash at app run
« on: October 12, 2010, 11:15:29 pm »
Quote from: "AdrianC"
I would create another project, enter all the linker settings and try again.


Nope. Still doesn't work.

Quote from: "AdrianC"
If that still doesn't work, I would download vs 2008, and try using the precompiled version of SFML.


Thats not a solution at all, thats surrender. I will never surrender, I will solve this problem!  :lol:

Thanks for your help though. I really appreciate it.

Anyone else want to take a crack at the problem?

8
General / Crash at app run
« on: October 12, 2010, 10:47:30 pm »
Thats not the problem. We already worked through that. Like 5-6 times already. All of that is 100% correct.

9
General / Crash at app run
« on: October 12, 2010, 06:56:46 pm »
I have no idea where your getting your tutorials. I got my code from this one here: http://www.sfml-dev.org/tutorials/1.6/window-window.php

It compiles just fine, only throwing the error when run, which probably points to a problem outside the code itself, in the compiler or runtime environment of some sort.

I tried your code, and it doesn't even compile. It throws a linker error ( 1>MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol _WinMain@16 referenced in function ___tmainCRTStartup )

EDIT: My friend just tried what may be one of his last ideas. He set up the first tutorial's code here: http://www.sfml-dev.org/tutorials/1.6/start-vc.php in a VS2010 project, and included the SFML files in the project itself. He zipped it and place it here: http://www.mediafire.com/?0p9aawl9lpxy1fu Totally setup to compile with no problems, it compiles on his end just fine (and should on anyone else's with VS2010. On my end I get the same error: http://img833.imageshack.us/img833/3578/nopedotavi.png

I am stumped. Anyone got any ideas?

10
General / Crash at app run
« on: October 12, 2010, 05:34:34 am »
Every time I run an app with SFML it crashes with an error message similar to the following:



This happens with any app that involves SFML, regardless of the content. Even the sample time test code crashes with this error.

I am running Visual Studio 2010. My friend compiled the latest version of SFML in VS2010 for me. Even then I continue to get the error. My friend, using the exact same code, and the exact same library files, compiles and runs just fine.

My compiler settings (linkers, includes, etc) are all correct.

I am attempting to use the dynamic, debug versions of the libraries.

I am on Windows 7 Ultimate 64-bit.

Pages: [1]