Debug Assertion failed - s3

hello Ragezone community!

I've got some weird problem.

when i`m trying to run my season 3 files everything is working and all fine.
i`m runing GS and go to Main.exe

when game is on .

the following error appears. and i can't do nothing as chatting on game or using some command.

here is a screenshot:
Screenshot by Lightshot

P.S.: i've got the source files.

thanks for any help.

Cheers.

Maybe u gotta install visual redistrutables 2005 then 2008 and then 2010 and be sure u got .net framework 3.5

Quote:

---

Originally Posted by KarLi

Maybe u gotta install visual redistrutables 2005 then 2008 and then 2010 and be sure u got .net framework 3.5

---

i already install redistrutables package.
here is screen shot from Debugging source files:



https://forum.ragezone.com/cache.php...%2FesuF1zV.png

https://forum.ragezone.com/cache.php...%2F7rUYAlH.pnghttps://forum.ragezone.com/cache.php...%2FBMbSTvK.png

well wit for ppl who know coding and they ll tell u.

Quote:

---

Originally Posted by KarLi

well wit for ppl who know coding and they ll tell u.

---

skye: OSher174

Quote:

---

Originally Posted by KarLi

well wit for ppl who know coding and they ll tell u.

---

you dont know coding ? O.o

Up.....

Quote:

---

Originally Posted by barak1991

you dont know coding ? O.o

---

Not really not :D

Without knowing further details of MU Online or it's source:

At some place in the code the C-function "fputs" is called with an empty stream. This is likely to happen if something in the code opens a file and calls "fputs" to write to it. The opening of a file fails and this failure is not handled in the code.

The following code would reproduce this behavior:

Code:

---

[...]
pFile = fopen ("file.xxx","a"); // <- Returns NULL if the opening of the file fails.
fputs ("Hello",pFile); // NULL gets passed as stream to fputs
[...]

---

You must provide error handling for such code!

You would now have to find where something like this happens in your code.

If you have the debug symbols, attach your visual studio debugger to the process. In the assertion dialog you have some option to "Retry" in order to start the debugging on the faulty instruction. Then check the call stack and find out where some file is being opened unsuccessfully.

Hope it helps you a little.

Quote:

---

Originally Posted by Future

Without knowing further details of MU Online or it's source:

At some place in the code the C-function "fputs" is called with an empty stream. This is likely to happen if something in the code opens a file and calls "fputs" to write to it. The opening of a file fails and this failure is not handled in the code.

The following code would reproduce this behavior:

Code:

---

[...]
pFile = fopen ("file.xxx","a"); // <- Returns NULL if the opening of the file fails.
fputs ("Hello",pFile); // NULL gets passed as stream to fputs
[...]

---

You must provide error handling for such code!

You would now have to find where something like this happens in your code.

If you have the debug symbols, attach your visual studio debugger to the process. In the assertion dialog you have some option to "Retry" in order to start the debugging on the faulty instruction. Then check the call stack and find out where some file is being opened unsuccessfully.

Hope it helps you a little.

---

Skye: OSher174

Quote:

---

Originally Posted by Future

Without knowing further details of MU Online or it's source:

At some place in the code the C-function "fputs" is called with an empty stream. This is likely to happen if something in the code opens a file and calls "fputs" to write to it. The opening of a file fails and this failure is not handled in the code.

The following code would reproduce this behavior:

Code:

---

[...]
pFile = fopen ("file.xxx","a"); // <- Returns NULL if the opening of the file fails.
fputs ("Hello",pFile); // NULL gets passed as stream to fputs
[...]

---

You must provide error handling for such code!

You would now have to find where something like this happens in your code.

If you have the debug symbols, attach your visual studio debugger to the process. In the assertion dialog you have some option to "Retry" in order to start the debugging on the faulty instruction. Then check the call stack and find out where some file is being opened unsuccessfully.

Hope it helps you a little.

---

i already try to debug... the following errors.. appear on attached screenshot.
Can i get your help with skype?

Your Screenshots only show the built progress. Not the debugging...

Quote:

---

Originally Posted by Future

Your Screenshots only show the built progress. Not the debugging...

---

i`m not able to debug :
see: http://snag.gy/m7xSg.jpg
P.S: see inbox please :)

bump!