I used to fire up Codewarrior all the time and by default it would
open a window, load the source code, and wait at main(). You could
then set breadpoints or step thru the code.

Xcode debugger opens up the window and automatically runs the executable.
My small program finishs before I can hit pause or anything.

Do I need to set a breakpoint at main()? If so, how?

thanks.

Why not just set a breakpoint at the first line in your main function?

Hm, I can't find it now, but you can set a "symbolic breakpoint" on main, and add that directive to a file that is automatically parsed when gdb starts up. I don't have my books here, but if you can't figure it out by Wednesday, I'll fix it for you.

Good, at least my approach is valid. It's just the details that are eluding me.
I open up the breakpoint window, and there is just a little "blue" box or
something. I try alot of stuff (that doesn't work) and just close in frustration.

I'll keep plugging away at it. Probably posted too early.

New Hardware (mac mini), New OS (OS X), new IDE (Xcode), new compiler, linker, and debugger (GNU).

Like the McDonald's line goes: I'm lovin' it

clicking in the left margin of any source file places a breakpoint on that line...

Sweet! Well that was too easy. Thought I had to be in the Debugger proper before
I could set breakpoint, but abviously I'm full of it.

Auch, I thought you wanted some kind of snazzy catch-all solution. Ohwell, chalk one up for Keith.

Well, I'm too late to say anything useful, so...

WhatMeWorry Wrote:You could then set breadpoints or step thru the code.

That sounds delicious! Do you have the recipe?