[SDL] SDL Application crash...

[Kurt Nordstrom]

Dunno if this is your issue or not, but you've got an assignment inside of
a comparison here:


   if(screen = NULL)   {
      #ifdef _DEBUG_
         debugLog << "Error setting up screen.\n";
      #endif

      return false;
   }

Which is setting screen to NULL all of the time.

On Mon, Feb 6, 2012 at 9:22 AM, Dr. Quigley <joecool.17.3 at gmail.com> wrote:

> **
>
>
>
>  Mason Wheeler wrote:
>
>  Access Violation reading 0x00000004 means that you've got a pointer to a
> struct or object, and you're attempting to read a member of it, but the
> pointer is NULL. They're usually trivial to find if your debugger is set up
> correctly; just run under a debugger and when the error occurs, the
> debugger will take you right to it. (Sometimes. For some bizarre reason,
> Visual Studio's debugger has capturing this exception turned *off* by
> default! So you might have to enable it.) When you get there, that's what
> to look for: access of a null pointer.
>
>
>
>
> Thank you! I'll poke around, see if I can find it.
>
> _______________________________________________
> SDL mailing list
> SDL at lists.libsdl.org
> http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
>
>


-- 
http://www.blar.net/kurt/blog/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20120206/e7d6ae14/attachment.htm>