Skip navigation.
 
mlRe: cross development problem
FROM : Ed Wynne
DATE : Tue Jul 18 17:41:20 2006

On Jul 18, 2006, at 10:17 AM, Thomas Bauer wrote:

> 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.


I hate to be a skeptic, but releaseExclusiveAccess sanity checks 
itself against an internal reference count. Extraneous releases are 
essentially just no-ops. The only way it would cause harm is if the 
object upon which it was been invoked was invalid. Which makes me 
wonder...

Do you ever release a DRDevice? Its unlikely you would have to, since 
all the methods to get them from DR are get and not copy or create. 
Releasing DRDevices out from under DR is a very common mistake, and 
would cause this symptom.

-Ed

Related mailsAuthorDate
mlcross development problem Thomas Bauer Jul 17, 23:22
mlRe: cross development problem Ed Wynne Jul 17, 23:53
mlRe: cross development problem Thomas Bauer Jul 17, 23:56
mlRe: cross development problem Mike Blaguszewski Jul 18, 00:08
mlRe: cross development problem Uli Kusterer Jul 18, 00:59
mlRe: cross development problem Thomas Bauer Jul 18, 16:17
mlRe: cross development problem Ed Wynne Jul 18, 17:41
mlRe: cross development problem Thomas Bauer Jul 18, 18:46
mlRe: cross development problem Thomas Bauer Jul 19, 10:11
mlRe: cross development problem Ed Wynne Jul 19, 18:17