• 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: How exactly are we supposed to debug memory problems???
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How exactly are we supposed to debug memory problems???


  • Subject: Re: How exactly are we supposed to debug memory problems???
  • From: Scott Ribe <email@hidden>
  • Date: Thu, 17 Aug 2006 08:59:23 -0600
  • Thread-topic: How exactly are we supposed to debug memory problems???

> If all else fails, set a breakpoint on write and put a gdb condition
> on it:
>
> b write
> cond 1 (char*)strnstr((char*)$r4,"Your error message",$r5) != 0
>
> That's for ppc at least. For Intel, you'd have to figure out where
> the arguments are in the write function.

Thank you. I believe that will be a good workaround for this problem.

--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice


 _______________________________________________
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: 
 >Re: How exactly are we supposed to debug memory problems??? (From: Jonas Maebe <email@hidden>)

  • Prev by Date: Re: How exactly are we supposed to debug memory problems???
  • Next by Date: Re: xcode-2.4 cctools-622.3 ld and KEXTs
  • Previous by thread: Re: How exactly are we supposed to debug memory problems???
  • Next by thread: Re: How exactly are we supposed to debug memory problems???
  • Index(es):
    • Date
    • Thread