🔒 Locked

Runtime error. Help!

Started by ironique Jun 25, 2004 at 2:39 AM 5 replies 1.1k views

Original Post

Jun 25, 2004 at 2:39 AM

I've been trying to map the code from NeHe's tutorials to use forms in Borland c++ v6 rather than creating a window. I have managed to do this until tutorial 7 where I get runtime error: Project GLWindow.exe raised exception class EAccessViolation with message 'Access violation at address 69105380 in module 'atixxglxx.dll'. Read of address 00F90001'. Process stopped. Use Step of Run to continue The Code compiles and links withiout a hitch, but when I run it, I get this error. Any suggestions? If there's any other info u'd like me to post pliz let me know. Thanx.

ironique

Author

ironique

Jun 28, 2004 at 10:59 AM

Oh come on guys, help me out here, I'm sure someone out there has at least a suggestion? This error just wont go away. Suggestions?

_the_phantom_

496

_the_phantom_

Jun 28, 2004 at 11:11 AM

probably a memory error of some sort, at a guess you've given a duff pointer to GL which is whats causing the crash.

Use the debugger to get an idea of what went on before the crash, check pointers etc

Samith

305

Samith

Jun 28, 2004 at 2:31 PM

Have you tried debugging? You're probably using bad pointers or making OpenGL expect more data than you're giving it or something.

Structural

Jun 29, 2004 at 4:45 AM

Since you're causing an error in an external component I suggest commenting everything out, and slowly start adding stuff again.
I still havent found a good way of debugging external components. I heard that with visual studio you can hook an executable, but you'll need debug data in the executable (which is unlikely for a release exe from ATI) for any output to be useful.

So, comment/add it is. I'd start with the most recently added code.

ironique

Author

ironique

Jun 29, 2004 at 6:15 AM

Tried commenting out section by section but I still got the error. Then I tried changing the bitmap i was loading with the one used in tutorial 6 and guess what, it worked! Now how do you explain that? Could there be a problem with the bitmap loader code? By the way, I'm not using the glaux code for loading the bitmaps, kept getting an "unresolved external" error, searched the forum and discovered I wasn't the only one getting that error. NeHe was kind enough to provide a non-glaux code for loading bitmaps, which I have been using.

schue

Jun 29, 2004 at 6:33 AM

you should really start using a debugger.

commenting out code sometimes is important to hunt down a bug, but in the long run using a debuger will help you writing better code.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.