http://cpp.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59?format=rss Tribe.net. Local Connections http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#6000cfd8-c594-4dd6-ab3a-c3b24fa38c63 Alan, GDB will help a lot, once you get used to how to run it. Apple's version has hooks that let XCode do the graphical debug thing, but that's Apple's own, and if you're ever on another *nix without XCode, knowing some basics on GDB will help. If you post or send some of your C code, I can help you debug it if you wish. Regards, John Falling You - exploring the beauty of voice and sound http://www.fallingyou.com Wed, 14 Dec 2005 02:57:24 GMT http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#6000cfd8-c594-4dd6-ab3a-c3b24fa38c63 John Michael 2005-12-14T02:57:24Z http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#7a68d7f3-b3e1-4a8b-a0d2-8c1d0b63fd54 Excellent suggestion, Seth. Thank you! Since I've been working Matlab, I've had very little need for the debugger so I'm pretty unfamiliar. The C programs I'll be writing and working with will be run in the Unix environment. Do you guys think it would be best to use a debugger such as GNU's GDB or should i try something else? Wed, 14 Dec 2005 02:29:14 GMT http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#7a68d7f3-b3e1-4a8b-a0d2-8c1d0b63fd54 $item.owner.firstName 2005-12-14T02:29:14Z http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#682a03fa-7dc1-4cc0-a57b-af401ba79ee2 I would put in some print to screen statements such as "spot 1", "spot 2", "Got this far 1", "Got this far 2", etc. in various places in your code, in each loop for sure, and then run the code. Then you can see how far into your code the program is running, or if it gets stuck in a loop, you will see the same "spot 5" or what ever a million times on your screen. Its worth trying... Wed, 14 Dec 2005 01:37:51 GMT http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#682a03fa-7dc1-4cc0-a57b-af401ba79ee2 Seth 2005-12-14T01:37:51Z http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#f3eb9b2c-2159-4b96-8f8d-7cbb92e2c8e1 Try tracing it with a debugger. Tue, 13 Dec 2005 23:34:47 GMT http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#f3eb9b2c-2159-4b96-8f8d-7cbb92e2c8e1 Bob 2005-12-13T23:34:47Z http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#68b69942-1197-45a0-a269-6d8e533c9297 So, I'm in the process of learning C. I have about a year and a half of programming experience in Matlab. I'm working through Brian Kernighan's "The C Programming Language" and I keep running into problems with my programs hanging. They compile just fine but I don't get any output. It's as if they're caught in a loop they can't get out of. I've double checked my code and it looks just fine (coming from the book). Anyone have any ideas? I'm working on a Mac G4 and compiling using gcc in unix. Love to hear any ideas. Tue, 13 Dec 2005 23:17:30 GMT http://CPP.tribe.net/thread/6bbd6b32-c822-46f2-b7ca-9cf2c8d2cb59#68b69942-1197-45a0-a269-6d8e533c9297 $item.owner.firstName 2005-12-13T23:17:30Z