• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: XCode 3.0 debugger - almost non-functional
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode 3.0 debugger - almost non-functional


  • Subject: Re: XCode 3.0 debugger - almost non-functional
  • From: Jonathan del Strother <email@hidden>
  • Date: Thu, 1 Nov 2007 18:35:54 +0000

Same here - I don't know what's happened to Stabs, but I've had all sorts of problems with it recently (I'm sure it didn't used to be this bad...). Switching over to Dwarf seems to have fixed 90% of our debugging troubles

On 1 Nov 2007, at 18:19, Dave Thorup wrote:

I had some problems similar to this when debugging a project that used different formats for the debug symbols - the frameworks the project was using were built with Stabs debugging info while the project was using DWARF. I couldn't load much, if any source code for the frameworks while debugging and stepping through things often resulted in the behavior you mention. The solution was to build the frameworks with DWARF debug symbols as well to match the project (I probably could have modified the project to use Stabs as well). The framework I was using is Qt.

So it could be a problem of different debug symbol formats mixed in your project that causes the debugger to get confused.
--
Dave Thorup
Software Engineer
http://bibblelabs.com



On Oct 31, 2007, at 8:31 PM, Doug Knowles wrote:

Hi,

I'm trying to get an app under development working under Leopard, and the debugger is proving almost useless. There's plenty of room to believe that I'm doing something wrong, so I'll post my observations and see what shakes out:

- Often, when the debugger stops at a breakpoint, the call stack is displayed, but the variable pane is blank.

- Often, single-stepping sends the app and the debugger into limbo; I never reach the next line, and about all I can do is terminate the app and start over.

- Almost always, threads other than the main thread can't be examined. As soon as I switch to another thread, the debugger display stops updating, and even the console window is non- responsive.

Maybe these are all related, and/or there's some setup I'm missing.

Any advice welcome.

TIA,
Doug K;




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: XCode 3.0 debugger - almost non-functional (From: Dave Thorup <email@hidden>)

  • Prev by Date: Re: Xcode 3.0 remarks
  • Next by Date: atos and DWARF
  • Previous by thread: Re: XCode 3.0 debugger - almost non-functional
  • Next by thread: atos and DWARF
  • Index(es):
    • Date
    • Thread