• 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: Tue, 4 Apr 2006 12:55:08 -0700

On 4 Apr 2006, at 11:01, John Draper wrote:
You can find leaks by setting the MallocStackLogging environment variable, but this does take time (and memory).

Yes, of course you can remove it later. Though it's easiest to simply uncheck it in that dialog, so you can turn it on again as needed. (In my normal work, I leave it on so I can check for leaks as fancy takes me, since the performance penalty isn't noticeable.)

yes - I intend to do the same thing.... but when I bring up the console, I get a lot of this...


Looking for devices matching vendor ID=1193 and product ID=8718

1. You don't use the console for this, you use the terminal 2. That's probably your scanner driver. Google for that string.

This looks like "leaks" but without a stack trace, so perhaps with a release build.

I have NO CLUE what you're talking about.... could you elaborate on that? Do you
mean this is output from a release build? I looked at the stack trace, I just didn't
send it.

Release builds often have symbols stripped. The stack trace is the interesting part, it tells you where memory was allocated.


Call stack: [thread 8bd7]: | 0x0 | _dyld_start | _start | main | 0x92eba25c | 0x92ecbbe8 | 0x92eba3f4 | 0x92e3b55c | 0x92ee42f8 | 0x92df28bc | 0x90a2e750 | -[mySipController awakeFromNib] | - [SipBridge initWithController:] | resip::infoServer::infoServer() | _ZN5resip10infoServerC4Ev | operator new(unsigned long) | malloc | malloc_zone_malloc

I looked at my source code, but what is this? "_ZN5resip10infoServerC4Ev" I don't have such
a class or function. How can I interpret this? I know the previous one... the code is...

Looks like a mangled name, but C++filt isn't unmangling it...

mInfoServer = new infoServer;
mInfoServer->SetServerInfo(self, serverport, serverport, "213.167.79.25", "213.167.79.20");


Is this the statement that correllates to "resip::infoServer::infoServer()" when I construct my
"InfoServer" object? I dived into this one, I could not find ANYTHING that relates to this
"_ZN5resip10infoServerC4Ev" I'm getting, whats up with this?

The leaked allocation was apparently inside your constructor (NOT SetServerInfo).


I did get the MallocDebug to work, but my tests didn't come up with any substantial reason why the
program crashes after a few minutes of running.

Did you turn on MallocGuardEdges, MallocScribble, MallocPreScribble? These are environment variables you can set via Xcode (or a terminal session).


Is there anyone on this list experienced in "thread safety"? I looked at the Apple App Notes on it,
and every AppNote I could find on the subject.

Try <http://lists.apple.com/mailman/listinfo/mt-smp>

David Dunham   http://www.pensee.com/dunham/
Imagination is more important than knowledge. -- Albert Einstein

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

  • Follow-Ups:
    • Re: Seeking advice on debugging "real time" programs.
      • From: John Draper <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: 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: John Draper <email@hidden>)

  • Prev by Date: Re: Seeking advice on debugging "real time" programs.
  • Next by Date: Re: Seeking advice on debugging "real time" programs.
  • Previous by thread: Re: Seeking advice on debugging "real time" programs.
  • Next by thread: Re: Seeking advice on debugging "real time" programs.
  • Index(es):
    • Date
    • Thread