Goober
2003.04.04, 10:12 AM
Hi there.
I'm getting a problem when trying to debug my game (ported from Windows) on OSX. I thought the best/easiest way to do this would be to use SDL, and I have a version of the game running under Windows that uses SDL (there is also a native Windows version).
The problem is I want to debug my app under OSX to sort out some porting issues (mostly to do with the file formats), but whenever I try debugging the app GDB has a fit and comes back with the following messages:
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).
The SDL framework is actually installed to /Library/Frameworks, so I don't know why the debugger is looking near the executable (which is somewhere on my desktop).
I managed to get so far with just outputting debug information to a file as the app runs, but I've hit a brick wall with that and I need to debug properly. As you can see, this is proving to be somewhat troublesome.
Thanks for any help,
Goober
I'm getting a problem when trying to debug my game (ported from Windows) on OSX. I thought the best/easiest way to do this would be to use SDL, and I have a version of the game running under Windows that uses SDL (there is also a native Windows version).
The problem is I want to debug my app under OSX to sort out some porting issues (mostly to do with the file formats), but whenever I try debugging the app GDB has a fit and comes back with the following messages:
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).
The SDL framework is actually installed to /Library/Frameworks, so I don't know why the debugger is looking near the executable (which is somewhere on my desktop).
I managed to get so far with just outputting debug information to a file as the app runs, but I've hit a brick wall with that and I need to debug properly. As you can see, this is proving to be somewhat troublesome.
Thanks for any help,
Goober