Panther and SDL -- NSInternalInconsistencyException

Hi,

I'm new to the list, so I apologies if this has been mentionned before. I

took a quick look in the archives and didn’t see anything similar …

I'm currently starting some work on my Master in CS and a part of the

project requires me to implements some tools that will work on Windows,
Linux, FreeBSD and MacOSX. SDL seems a logical choose for this. I’ve got
everything working on Windows, and almost everything on Linux. MacOSX is
giving me a huge headache …

After doing some reading for hours, I've managed to compile a small example

(thanks to sdl-config). However, when I run it on MacOSX, I get several
"Object autoreleased with no pool in place errors" and then crashes with a "
Uncaught exeption: Error (1002) creating
CGSWindow Trace/BPT trap ". Being new to MacOSX, I have not idea what that
means. Searching on newsgroups has revealed one person having the same
problem (posted yesterday) and no solution.

What I’m using:
MacOS X 10.3 Panther (almost fresh install)
SDL 1.2.6 compile from source
G++ 3.3 20030304 Apple Build

I want to stick to makefiles to make everything as portable as possible.

Thanks for any help.

Alexandre

After doing some reading for hours, I’ve managed to compile a small example
(thanks to sdl-config). However, when I run it on MacOSX, I get several
"Object autoreleased with no pool in place errors" and then crashes with a "
Uncaught exeption: Error (1002) creating
CGSWindow Trace/BPT trap ". Being new to MacOSX, I have not idea what that
means. Searching on newsgroups has revealed one person having the same
problem (posted yesterday) and no solution.

See last post about SDL_main.

–ryan.

After doing some reading for hours, I’ve managed to compile a small
example
(thanks to sdl-config). However, when I run it on MacOSX, I get several
"Object autoreleased with no pool in place errors" and then crashes
with a "
Uncaught exeption: Error (1002)
creating
CGSWindow Trace/BPT trap ". Being new to MacOSX, I have not idea what
that
means. Searching on newsgroups has revealed one person having the same
problem (posted yesterday) and no solution.

Alexandre,

Many people have had this problem. Check that you are linking to
SDLMain (should have -lSDLmain on the link line), and that your main
routine is renamed to SDL_main (#include SDL.h in main.c). sdl-config
should be doing this for you, but apparently it is not.On Dec 13, 2003, at 3:02 PM, sdl-request at libsdl.org wrote: