Hello all,
My apologies for barging in so abruptly. Normally I'd lurk for a few days, get familiar with the list before posting.
But the pressure's on, as always when doing code. I did read the FAQ and do an Archives search on my problem, no joy, before coming here.
Briefly, when trying to use XCode 2.4.1 on 10.4.8 (or 9) to debug a little Cocoa app that started life in IB and has had very little added since then, I get the following message in the Debugger, and gdb becomes sullen and won't do anything useful after that till I kill it and start a new debug run:
GDB: Timed out fetching data. Variable display may be inaccurate.
Often happens when I haul up the Expressions window and do a bit of typing. Since it usually happens within the first minute or so of a debug run (unless I click and clack quickly on Step In/Over/Out, which seems to hold it at bay for a while), obviously it reduces the debugger almost to uselessness for my needs.
Less briefly, I'm a newbie at OS X programming, working for the first time in Obj-C, and moving to OS X a small project that originated on Windows. Have programmed many years for HP and Agilent, but in UN*X environments and proprietary OSs.
MacBook w/2GB RAM, 160GB of disk, 10.4.9, I installed XCode 2.4.1 3-4 days ago, no substitute shells or debuggers, etc, no Haxies or odd KEXTs or other risky stuff. I guess it could be an install problem, but seems unlikely since the XCode install went normally. Am building a Cocoa vanilla app with default settings for the project. The one place I added some code other than the necessary #includes of IB-genned headers is in an action method on my controller object, where I wrote about 10 lines of C that uses some stdio (just to fopen() a disc file, and a fscanf()), which I don't believe to be the problem because gdb often stalls before I execute that code.
So, did I miss the memo or something? Do I need to make a secret XCode setting? Is gdb known not to work well under XCode? I'd have expected an uproar on the list if so, but I see just a few non-earth-shattering complaints about gdb, mostly from 2004 and earlier, as I'd expect.
Or is it more likely something wrong in my install?
Can anyone on the list advise me what to do next?
I haven't used gdb before, but if I have to, I'll learn to run it from the shell. But I'm still hoping for a "pleasant", XCode-based debugging experience.
BTW, FWIW I think XCode is much easier to use than, though not as baroque and completist as VS and VS .NET et al. I didn't have to use those devil-spawn very much while I was at HP and Agilent, and I'm hoping XCode will allow me to continue avoiding them (and oh god, Win32), right up until the final backport, test/tune, and prep of the ROM image (embedded vision app, but who wants to do basic algorithm work from a PC via an ICE to a DSP? Mac will be much nicer, Cocoa will make adding filters, etc on the fly much easier).
Many thanks for any help anyone can provide.
"He dreamed of some day becoming a bum, but he's too lazy"
Scott F Bayes 080-6616-1554 (mobile)
|