Thanks for the log.
Interesting the log stops in the middle of a gdb command => is it possible you copied it while lazarus was still running, or you killed lazarus from the process-manager?
In those 2 cases the log may not have been flushed.
You can try and select "reset debugger" from the run menu. it may not actually work, if the debugger is hanging like this (an issue that needs to be fixed, if the case) but it should add additional output to the log, ensuring it isn't cut off, by an improper file-close.
---
it appears you may have no debug info, that should not lead to a hang, but will give problems anyway:
From the log
1/9/11 5:27:46 PM [0x0-0xe80e8].laz_svn[3742] TCompiler.Compile WorkingDir="/Users/phil/laztests/teststringgrid/" CompilerFilename="/usr/local/lib/fpc/2.5.1/ppc386" CompilerParams=" -MObjFPC -Scghi -O1 -gl -WG -vewnhi -l -Fi/Users/phil/laztests/teststringgrid/lib/i386-darwin -Fu/Users/phil/laz_svn/lcl/units/i386-darwin -Fu/Users/phil/laz_svn/lcl/units/i386-darwin/carbon -Fu/Users/phil/laz_svn/packager/units/i386-darwin -Fu/Users/phil/
1/9/11 5:27:46 PM [0x0-0xe80e8].laz_svn[3742] laztests/teststringgrid/ -Fu. -FU/Users/phil/laztests/teststringgrid/lib/i386-darwin/ -oproject1 -dLCL -dLCLcarbon project1.lpr"
it has -gl, but neither -g -gs nor -gw
If that is correct, then you need to add eithe -g or -gw (stabs or dwarf) in the linking tan of the project options.
----
Another thing you can do (*before* you add debug info):
Test some things by hand in gdb.
Run:
gdb -i mi lazarus
or
gdb -i mi ./lazarus.app/Content/MacOs/lazarus
then in gdb type the following. And after each command take special note, that gdb returns *after* all output: "(gdb)" which is the prompt for the next command.
It has been seen that gdb omits this prompt (it shouldn't, but...), yet gdb is ready for the next command. However the IDE will never learn this, as it waits forever for that prompt...
Here are the commands to try:
-gdb-set language pascal
info address main
=> may give warnings, but return something like
"main\" is at 0x1196c in a file compiled without debugging.\n""
convert address to decimal and execute (with correct address)
-break-insert -t *72044
=> watch out for gdb prompt
try execute:
ptype TObject
just to see and try to find out where it hangs....
----------
And yes: the error checking, and (it any at all) error msgs returned by the IDE for debugging are not useful at all....
On the todo list....