On Mac OS X with the SDL development libraries, debugging a SDL
Application project fails. The Project Builder debug tab’s console
reports the message below, and the application never launches. I am
unsure if this is is a problem with my configuration or a limitation of
the SDL library.
warning: Unable to read symbols from
"@executable_path/…/Frameworks/SDL.framework/Versions/A/SDL"; reading
from memory.
/SourceCache/gdb/gdb-250/src/gdb/macosx/macosx-nat-dyld-process.c:505:
internal-error: assertion failure in function “dyld_load_library”:
e->dyld_valid
A problem internal to GDB has been detected. Further
debugging may prove unreliable.
The Debugger has exited due to signal 6 (SIGABRT).
FWIW, I get the same error, I haven’t been able to figure out if it was
a config issue or not.
OSX 10.2.6
JimOn Wednesday, June 25, 2003, at 04:39 PM, john philip wrote:
On Mac OS X with the SDL development libraries, debugging a SDL
Application project fails. The Project Builder debug tab’s console
reports the message below, and the application never launches. I am
unsure if this is is a problem with my configuration or a limitation
of the SDL library.
warning: Unable to read symbols from
"@executable_path/…/Frameworks/SDL.framework/Versions/A/SDL"; reading
from memory.
/SourceCache/gdb/gdb-250/src/gdb/macosx/macosx-nat-dyld-process.c:505:
internal-error: assertion failure in function “dyld_load_library”:
e->dyld_valid
A problem internal to GDB has been detected. Further
debugging may prove unreliable.
The Debugger has exited due to signal 6 (SIGABRT).
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
On Mac OS X with the SDL development libraries, debugging a SDL
Application project fails. The Project Builder debug tab’s console
reports the message below, and the application never launches. I am
unsure if this is is a problem with my configuration or a limitation
of the SDL library.
warning: Unable to read symbols from
"@executable_path/…/Frameworks/SDL.framework/Versions/A/SDL";
reading from memory.
…the problem is that the symbols are being looked for in the
@executable_path (i.e. inside the application bundle)…
…the way around this is to add a “copy files” build phase, and copy
the sdl framework into the application’s framework directory…plenty
more info if you search the previous list posts…
l8r,
jamieOn Thursday, June 26, 2003, at 01:05 AM, James Kersey wrote:
On Wednesday, June 25, 2003, at 04:39 PM, john philip wrote:
It has to be something related to your configuration, since I’m being
able to rebug SDL applications (in windowed mode) withou any problem.
I’, using OS X 10.2.6.
john philip wrote:> On Mac OS X with the SDL development libraries, debugging a SDL
Application project fails. The Project Builder debug tab’s console
reports the message below, and the application never launches. I am
unsure if this is is a problem with my configuration or a limitation
of the SDL library.
warning: Unable to read symbols from
"@executable_path/…/Frameworks/SDL.framework/Versions/A/SDL"; reading
from memory.
/SourceCache/gdb/gdb-250/src/gdb/macosx/macosx-nat-dyld-process.c:505:
internal-error: assertion failure in function “dyld_load_library”:
e->dyld_valid
A problem internal to GDB has been detected. Further
debugging may prove unreliable.
The Debugger has exited due to signal 6 (SIGABRT).
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl