• 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: Can't trace into an Obj-C call?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can't trace into an Obj-C call?


  • Subject: Re: Can't trace into an Obj-C call?
  • From: Rick Mann <email@hidden>
  • Date: Wed, 14 Nov 2007 09:29:20 -0800


On Nov 14, 2007, at 7:45 AM, Rick Altherr wrote:

What you are seeing is a tail-call optimization. Since the method just simply calls another method, the stack frame gets reused.

Ah! Of course. I should've recognized this.

Too bad GDB can't figure out how to trace into it, but that's okay. Turning off optimizations was fine.

--
Rick

_______________________________________________
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: 
 >Can't trace into an Obj-C call? (From: Rick Mann <email@hidden>)
 >Re: Can't trace into an Obj-C call? (From: Dave Camp <email@hidden>)
 >Re: Can't trace into an Obj-C call? (From: Rick Mann <email@hidden>)
 >Re: Can't trace into an Obj-C call? (From: Rick Altherr <email@hidden>)

  • Prev by Date: Re: Where did the Clear Log button go in Xcode 3
  • Next by Date: Re: Creating a Carbon Framework with header files in multiple directories.
  • Previous by thread: Re: Can't trace into an Obj-C call?
  • Next by thread: Change Application Name
  • Index(es):
    • Date
    • Thread