• 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: cross development problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cross development problem


  • Subject: Re: cross development problem
  • From: Thomas Bauer <email@hidden>
  • Date: Tue, 18 Jul 2006 16:17:25 +0200

Hi!

Thanks for all your suggestions.
I tried out everything to find out what most of you already suggested.

it had nothing to do with the compiler settings.
It actually was a legacy releaseExclusiveAccess after the DRErase that for some reason
crashed the program in 10.3 but not in 10.4.
The other issues where all seperate bugs invisible in 10.4.


The main trouble for me was testing it without having to convert
the project back to a XCode1 (the only one that would run in panther).
Which was of course very inconvienient.
If such bugs are not reproducable on the development machine
is there any other easy way to debug it for an older system?

thanks and kind regards
Thomsa

On Jul 18, 2006, at 12:59 AM, Uli Kusterer wrote:

Am 17.07.2006 um 23:56 schrieb Thomas Bauer:
On Jul 17, 2006, at 11:53 PM, Ed Wynne wrote:

Sounds like you have a memory corruption problem. DR is especially sensitive to its objects being over-released at the end of burn / erase cycles when it cleans up and does its own internal house keeping chores.

Well, using a DRErase is not very much magic,
and why would that only affect 10.3 and never occur in 10.4?
Plus, this is not the only issue. There are also others like the carbon code that does not work all of a sudden,
random crashes even leading to the Finder logging out the user etc.
Nothing of that sort in 10.4 on ppc nor intel.

It's in the nature of memory bugs that when you screw up some memory it may behave in very nondeterministic ways, because on every installation memory is laid out differently.


If you're interested in reading more about this, I've written some articles on memory management on my web site, and I also touch this subject as part of the C tutorial there.

Cheers,
-- M. Uli Kusterer
http://www.zathras.de




_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: cross development problem
      • From: Ed Wynne <email@hidden>
References: 
 >cross development problem (From: Thomas Bauer <email@hidden>)
 >Re: cross development problem (From: Ed Wynne <email@hidden>)
 >Re: cross development problem (From: Thomas Bauer <email@hidden>)
 >Re: cross development problem (From: Uli Kusterer <email@hidden>)

  • Prev by Date: Re: Symmetric Distributed Objects
  • Next by Date: RE: Disabling Certain Title bar controls
  • Previous by thread: Re: cross development problem
  • Next by thread: Re: cross development problem
  • Index(es):
    • Date
    • Thread