• 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
Xcode Debugger: Cannot Step Into a Method in a x86_64 architecture build
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode Debugger: Cannot Step Into a Method in a x86_64 architecture build


  • Subject: Xcode Debugger: Cannot Step Into a Method in a x86_64 architecture build
  • From: Andreas Grosam <email@hidden>
  • Date: Tue, 13 Jan 2009 22:38:22 +0100

Hi,

Xcode Debugger will not step into a method in an Objective-C++ x86_64 build when clicking the "Step Into" command in the menu bar. There is no problem for a 32bit build, though. Of course, it is a Debug Configuration.

Xcode Debugger just skips over the message invocation and stops at the next statement. If I place a breakpoint within the method, the Xcode Debugger stops there as expected. The method actually will be called, the receiver is not nil, and the method exists ( the compiler also does not generate a warning, that the method might not be called).

The initial build settings came from a template project. It worked ok, unless I switched to 64 bit arch.

After experiencing this, I also tried different build settings (in combination with 64bit arch):
- changed the Debugging Format to DWARF with dSYM file.
- selected version 4.2 of the C/C++ Compiler
- unchecked Accelerated Objective-C Dispatch
- unchecked Fix and Continue
to no avail.



This is also noteworthy: Stepping into a C++ constructor defined in a method works as expected.

@try blocks and C++ d-tors:
When a C++ instance is defined within a @try-block and leaves scope due to an Objective-C exception, stepping out of this block (with command Step Into) does not step into the d-tor of the instance, which IMHO should be the case. The d-tor will be called as expected, though. If a breakpoint is set within the d-tor, Xcode Debugger will stop there as expected. Note that this is only implemented in the 64bit runtime - in the 32 bit runtime the different exception schemes are not compatible.


So, can I convince the debugger to do what I want - or is this a known problem (sorry, I wasn't on this list for quite a while so I might have missed some important things)?


Thanks in advance for hints and tips

Andreas


Xcode version: 3.1.2 on a brand new MacBook Pro, haveing same nasty WiFi problems ;) _______________________________________________ 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
  • Follow-Ups:
    • Re: Xcode Debugger: Cannot Step Into a Method in a x86_64 architecture build
      • From: "Sean McBride" <email@hidden>
  • Prev by Date: Re: //Comments
  • Next by Date: RE: //Comments
  • Previous by thread: Re: //Comments
  • Next by thread: Re: Xcode Debugger: Cannot Step Into a Method in a x86_64 architecture build
  • Index(es):
    • Date
    • Thread