Crash that I cant debug.

[lukem]

Hello , working on my project I encounter a crash to windows. I'm digging the code but the error sometimes show sometimes not. The problem is - there is no correct way to identify the source of the problem, other way than guessing.

Here is a screenshot of exception thrown (it is an image because in that stupid windows there is no way to copy the text):



it also produces a log which looks like this:
http://pastebin.com/URUttCZt

I'm looking for an explanation but it's almost impossible to find. The best would be just to know what is actually wrong and how can I read such an error log. This creates a lot of mess especially in a relatively big system like mine (scene graph and other things, like GUI).

So if anybody has a solution or at least an advice or experienced something like that - I would be glad for help.

[matanui159]

I once had a crash like this...
I forgot what the problem was...
If you gave me some code snippets, it would probably help...

[Cornix]

I usually get these kinds of crashes when something about the buffers is wrong. Bad positions / limits when trying to read or write to VBO's or other data structures.

[abcdef]

If you have a vertex buffer and you update it but have a larger data set than then you first created you could get JVM crashes. I have seen this myself

[quew8]

I agree with what has been said above but just a little note: if you are referring to the Command Prompt by

that stupid windows

then you can right click on the title bar in Command Prompt and go to the "Edit" sub menu where you will find all the useful edit functions.

And (not that I'm comparing Windows to Linux, I'm all for Linux but in the interests of giving credit where it is due) as far as I know this is actually more than you can do in all the Linux distros I've worked with. Sure you can pipe the output to a text file but you can do exactly the same in Windows.