[bobrocke]

How do I view variables more complicated than ints and Bool while debugging?

I'd like to "see" the contents of NSStrings and other structures.

What's the trick?

Bob

------------------
Bob
-----------
Robert J. Rockefeller
Jackson, Mississippi
"I'm growing older, but not up!"

[Apocalypse]

There should be a variable named "self" in the listing. Hit the triangle to open it and you should get all the variables in the class that you are in. As I recall (bear with me I am not at my system right now), you can also hit that triangle to get a drop-down of the value and reference of the variable (it might be in another sub-section called "isa").

Give it a try and tell me if that worked,
Jeff.

[wadesworld]

Currently you have to use the gdb console. (That will change later)

When you're stopped at the breakpoint, you'll see a little console tab at the top - pull that down. That exposes the gdb console.

Then type:

po mystring (or whatever your object name is)

po is short for print-object

You can do all sorts of neat things with the gdb debugger, like when it hits a breakpoint, print the object to a file, then continue running. This would allow you to watch values change through the course of your program, without having to stop and look at them each time. Then you can use tools like grep to search through this huge file, and find out exactly what you're looking for.

That's just a simple example. I'm looking forward to more functionality being exposed in the GUI, but I also like having the power of the command-line gdb available.

Wade

[bobrocke]

The po command in GDB does the trick.

I'm more used to, and like better, the very flexible visual debugger in the CodeWarrior IDE. So I'm looking forward to more power in the GUI part of the Project Builder debugger.

Thanks for your help!

Bob

------------------
Bob
-----------
Robert J. Rockefeller
Jackson, Mississippi
"I'm growing older, but not up!"