• 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: Memory debuggers for MacOS 10.3.9
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory debuggers for MacOS 10.3.9


  • Subject: Re: Memory debuggers for MacOS 10.3.9
  • From: "D. Walsh" <email@hidden>
  • Date: Fri, 28 Oct 2005 20:27:14 -0400
  • Mta-interface: amavisd-new-2.3.3 (20050822) at daleenterprise.com


On Oct 28, 2005, at 14:09 , Mark Wagner wrote:

On 10/27/05, D. Walsh <email@hidden> wrote:


On Oct 27, 2005, at 04:01 , Jonas Maebe wrote:



On 27 Oct 2005, at 00:00, Mark Wagner wrote:



 I don't happen to have access to 10.4, so are there any
memory debuggers that work on 10.3.9?



You could try electric fence, it's similar to GuardMalloc: http://perens.com/FreeSoftware/ElectricFence/

I've never tried it under OS X, but don't see why it wouldn't work.


Jonas


I looked at this before, it doesn't build in Mac OSX unless you comment out line 33 of page.c but then it still failed so digging deeper into the source I determined that it required a switch.


Thanks. I found the memory bug that's been plaguing me for some time: CodeWarrior/CFM does not provide a "uint" type, so our code defines it in a header file as being 16 bits. GCC/Mach-O *does* provide it, so our header file doesn't -- but it's now 32 bits. Needless to say, this causes problems when trying to load 16 bits of data from a binary file.

I was having a similar issue myself, I had to find a solution for efence before I could fix my code problem which to most people doesn't make sense, they want a simple solution and don't realize that some times a better solution that isn't currently working is worth spending the time on fixing.


Can you post the output that led you to your problem so others can see what it looks like and possibly generate an interest in this tool?

I've expanded efence's functionality to cover some additional memory manipulations like exceeding the 4gb page boundry with contiguous code and added additional feedback and formating.

Generating the shared library makes adding efence to any project a breeze and it's unfortunate that this isn't a main-stream product because I feel it's a tool worth obtaining and using, of course this is just my opinion, what do I really know.

Thanks,
Mark Wagner

-- Dale

_______________________________________________
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: 
 >Memory debuggers for MacOS 10.3.9 (From: Mark Wagner <email@hidden>)
 >Re: Memory debuggers for MacOS 10.3.9 (From: Jonas Maebe <email@hidden>)
 >Re: Memory debuggers for MacOS 10.3.9 (From: "D. Walsh" <email@hidden>)
 >Re: Memory debuggers for MacOS 10.3.9 (From: Mark Wagner <email@hidden>)

  • Prev by Date: Re: mkdir in PhaseScriptExecution
  • Next by Date: std::map<>::iterator in Xcode 2.1
  • Previous by thread: Re: Memory debuggers for MacOS 10.3.9
  • Next by thread: code folding
  • Index(es):
    • Date
    • Thread