• 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: MallocDebug: Can it be used at all?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MallocDebug: Can it be used at all?


  • Subject: Re: MallocDebug: Can it be used at all?
  • From: Christopher Holland <email@hidden>
  • Date: Thu, 14 Mar 2002 15:47:37 -0600

Actually, I'm seeing the same thing here. I haven't messed with it much yet, so I can't even guess at a cause, though I can tell you that I don't have any of the Unsanity products installed, so that is probably not the cause (at least for me).

FYI, I have installed the following: TinkerTool, USBOverdrive, & Diablotin...although, I don't think any of those should cause any problems (save maybe TinkerTool). I figure that this might help sort out any commonalities between people who have the problems.

If I get around to fixing it, I'll let you know if I figure out anything.

Christopher

On Thursday, March 14, 2002, at 01:38 PM, Matthew Formica wrote:

I don't think I've ever seen MallocDebug lie. In this case, I bet your app
is interacting in a weird way with Unsanity products (WindowShade/X, etc.) -
try disabling them.

- Matthew

On 3/14/02 8:32 AM, "Timothy Ritchey" <email@hidden> wrote:

On Thursday, March 14, 2002, at 09:23 AM, Jonathan Feinberg wrote:

When I try to launch the built app with MallocDebug, I almost
immediately get a dialog stating that "Target application crashed:
/path/to/my/app accessed memory at 0x7c0802ae illegally."

If it is any consolation, I am seeing this as well. I assumed that I
wasn't doing something right, like linking with libMallocDebug.A.dylib,
or setting the -force_flat_namespace option that is suggested for
running a program separately from the MallocDebug application and
connecting to it. I couldn't even get my app to compile using
-force_flat_namespace.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: MallocDebug: Can it be used at all?
      • From: Timothy Ritchey <email@hidden>
    • Re: MallocDebug: Can it be used at all?
      • From: Eric Peyton <email@hidden>
References: 
 >Re: MallocDebug: Can it be used at all? (From: Matthew Formica <email@hidden>)

  • Prev by Date: Re: MallocDebug: Can it be used at all?
  • Next by Date: Re: MallocDebug: Can it be used at all?
  • Previous by thread: Re: MallocDebug: Can it be used at all?
  • Next by thread: Re: MallocDebug: Can it be used at all?
  • Index(es):
    • Date
    • Thread