• 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: Seeking advice on debugging "real time" programs.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Seeking advice on debugging "real time" programs.


  • Subject: Re: Seeking advice on debugging "real time" programs.
  • From: David Dunham <email@hidden>
  • Date: Wed, 12 Apr 2006 16:37:19 -0700


On 12 Apr 2006, at 14:37, John Draper wrote:

if checking for leaks is not part of your development process, you will *always* have leaks.

Yea - I know - one of the pitfalls of programming the Mac, but I suppose other platforms can
also experience this problem.

It has nothing to do with the Mac. Almost all the leaks I fix are introduced into our cross-platform code by programmers who're using Windows :-)


All I know about it, is what I read in
the Tech notes and docs, and we all know how useless these docs are when they (whoever wrote
them) don't have the common decency to at least put a few more examples in them. They fail
to give any details at all on what this "object" is that is passed to the @synchronize.

<http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/ Articles/chapter_4_section_9.html> seems pretty clear. It's essentially the unique identifier that other threads use to decide whether to block.


But I still have to turn on MallocStackLogging, right?

At least if you want to see the backtraces to your malloc events in the leaks report.

Right... but I would need to launch my application from X-Code right? Since I have the
"MallocStackLogging" set in the Executeable.

No, you can set environment variables in a Terminal window and launch from there.


I'm developing a VIOP Sip phone for the mac. [snip]

At least we get the complete background!

I would like to know if it's possible to put a "Watch" variable so when an Object is changed,
like when I add another item to a NSMuteableArray, it would break into the debugger.
Can that be done with X-Code?

Xcode's watchpoints appear to be overly scoped, though perhaps I'm missing something. (They're also going to seriously change your real- time performance characteristics!)


David Dunham       Development Manager
+1 206 926 5722      GameHouse Studios


Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: 
 >Seeking advice on debugging "real time" programs. (From: John Draper <email@hidden>)
 >Re: Seeking advice on debugging "real time" programs. (From: David Dunham <email@hidden>)
 >Re: Seeking advice on debugging "real time" programs. (From: j o a r <email@hidden>)
 >Re: Seeking advice on debugging "real time" programs. (From: John Draper <email@hidden>)
 >Re: Seeking advice on debugging "real time" programs. (From: j o a r <email@hidden>)
 >Re: Seeking advice on debugging "real time" programs. (From: John Draper <email@hidden>)

  • Prev by Date: C++ Compiler Mystery
  • Next by Date: Re: remote debugging, can't see source code
  • Previous by thread: Re: Seeking advice on debugging "real time" programs.
  • Next by thread: Mac keyboard as midi keyboard
  • Index(es):
    • Date
    • Thread