[quake3] Intel Mac Services
Scott Harper
orcein at gmail.com
Wed May 17 14:31:21 EDT 2006
I suppose I should be ashamed to admit this, but... I've never used a
debugger outside an IDE before... -.-;; I'm a master at XCode
debugging and NetBeans debugging. I've even done a little in
Eclipse. But I've never flat-out used GDB from the terminal. (Mac OS
X defauls to bash.)
Any hints? There's SO much documentation and code to go through, I
fear it could take at least a week or two until I know what I'm doing
if I have to go about this the long way (ie: finding docs and
tutorials online, AND looking through the code, etc...)
I can be found on IM (AIM, MSN, Yahoo) under the name "Lareon" if
someone wants to find me that way to help out. Or, I can be on the
IRC sometime; just let me know what time frame to be there (GMT works
for me as a general stating point).
I hope I don't come across as lazy in all this... I have some other
projects I'm working on, but feel that a good universal build of Q3
is noble enough to take some time away from them... I just can't
justify ALL my time away for it.
--Scott
On May 17, 2006, at 8:02 AM, Thilo Schulz wrote:
> On Wednesday 17 May 2006 02:01, Scott Harper wrote:
>> So, where would you like for me to start looking?
>
> I think the best thing you could do would to try to debug this
> thing with a
> debugger.
> GDB should work on OSX, too...
> To work around fullscreen mode and the crashing which will
> effectively freeze
> you with a black screen, you can start the debugging remotely using
> ssh or
> something.
> As soon as it crashes, it should indicate the position where it
> crashed if you
> included debugging symbols in the output file. A "backtrace" and a few
> printouts of a few variables at runtime would already give alot of
> clues more
> than your description.
>
> --
> Thilo Schulz
More information about the quake3
mailing list