• 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: Why MallocDebug shows HEX addressed but not C++ names?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why MallocDebug shows HEX addressed but not C++ names?


  • Subject: Re: Why MallocDebug shows HEX addressed but not C++ names?
  • From: Ruslan Zasukhin <email@hidden>
  • Date: Thu, 07 Aug 2008 08:41:22 +0300
  • Thread-topic: Why MallocDebug shows HEX addressed but not C++ names?

On 8/6/08 9:19 PM, "Ruslan Zasukhin" <email@hidden> wrote:

> On 8/6/08 8:51 PM, "David Dunham" <email@hidden> wrote:
>
>> On 6 Aug 2008, at 10:12, Ruslan Zasukhin wrote:
>>
>>> I have played with MallocDebug to see if leaks exists and it show
>>> me HEX addressed instead of names.
>>>
>>> YES - I run it app from XCODE
>>>         Run -> Start With Performance Tools -> MallocDebug
>>>
>>> YES - I run it on DEBUG target of app.
>>>
>>> YES - I have debug symbols ON, format DWARF
>>>
>>> YES - if click on address, it show correct debug dylib,
>>>         e.g. vserver_debug.dylib
>>>
>>>
>>> So where can be trouble? Anybody can give hint?

>> Did you set MallocStackLogging as an environment variable?
>
> No,
>
> Going todo google on this :-)
>
> Thank you, David.

Well, little butter but still not works as expected.
Let me describe in more details.

I have PROJECT of executable  Vserver,

    which is linked to vserver_debug.dylib,
        located in its BUILD folder

    which is linked to few others our dylibs
        located in folders /usr/local/lib/vcomponents
        (copied there by run script after build).

So after I have add for Executable vserver the environment variable
    MallocStackLogging  1   (in the properties window of executable)


I have start to see few levels of names of executable!  GOOD :-)

But I still do not see names from our DYLIBs   :-(
What magic steps I need todo to start see DYLIBs names?


P.S. Another issue not clear to me.
    I have try template New Project -> Standard C++ app.
    and this app works fine in MallocDebug. And there is no any
    MallocStackLogging environment variable for it.
    So why it works without it?
    Why my executable was need MallocStackLogging ?


--
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]


 _______________________________________________
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: Why MallocDebug shows HEX addressed but not C++ names?
      • From: Ruslan Zasukhin <email@hidden>
References: 
 >Re: Why MallocDebug shows HEX addressed but not C++ names? (From: Ruslan Zasukhin <email@hidden>)

  • Prev by Date: Re: Funky Xcode crashing-my-app behavior
  • Next by Date: Re: Why MallocDebug shows HEX addressed but not C++ names?
  • Previous by thread: Re: Why MallocDebug shows HEX addressed but not C++ names?
  • Next by thread: Re: Why MallocDebug shows HEX addressed but not C++ names?
  • Index(es):
    • Date
    • Thread