Using GDB without PB

[paul at eisusa.com (Paul Nicholson)]

At 6:20 PM +0100 3/15/02, Andreas Monitzer wrote:
>On Friday, March 15, 2002, at 06:01 , Paul Nicholson wrote:
>
>>I'm working on a plugin that builds from a terminal command line and I have yet to figure out how to get PB to build it as it appears that PB doesn't let me get  to the make file used.
>
>Project -> New Target -> Legacy Makefile

Thanks for the help. I managed set it up for a legacy makefile. WIth the terminal, I can build my project with "make -f make/test.make" or "/usr/bin/make -f make/test.make" from a command line. So I put that string into the "Build Tool" box in the "Custom Build Command" panel of the "Target" panel.

It won't make. Here's the error:

make -f make/test.make
Exception starting task (make -f make/test.make) ; name: NSInvalidArgumentException, reason launch path not accessible

The project is in the same directory as I run the terminal shell in. If I put "ls" or "cd" in for the "Build Tool" I get the same error. It looks like PB's choking on the build command line.

Any ideas?


>>Anway, assuming I can't build it with PB, is there a way to use PB to debug it? I noticed that GDB runs from a terminal window, but it looks brutal to use it that way - how would one get source display?
>
>In Terminal: gdb <path-to-executable>
>
>Use the command "list" to get the source display ("help" for help).

Say it ain't true. Is GDB and PB the state of the art in OS X debugging? Heaven help the one who needs to do some real debugging. I guess I'm spoiled, I've used Jasik's theDebugger for years to do a lot of application and driver debugging and I really like its rich interface. You can setup loads of windows to display data, code, register, stack, and switch between, source, assembly and mixed display.

Other than the simplified source code display you get in PB, GDB reminds me of rom monitor debugging on a RS-232 terminal.

Paul