• 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: Possible GCC Bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Possible GCC Bug?


  • Subject: Re: Possible GCC Bug?
  • From: Jean-Daniel Dupas <email@hidden>
  • Date: Tue, 8 Apr 2008 18:50:02 +0200



Le 8 avr. 08 à 18:31, Greg Knight a écrit :
Hi Folks,
 
I've been away from 'C' for over ten years, and just come back to port a legacy app to the MAC. The following code is misbehaving under the XCode 3.0 Debug configuration (GCC4). I'd appreciate any suggestions.
 
// int fred has value 13
DisposeWindow(WinData->window);    // Carbon call
// int fred now has value 27
 
This is burried in thousands of lines of code, and other calls to DisposeWindow(..) don't affect "fred" at all.
 
My nasty work-around for this is:
 
int Safefred = fred;
DisposeWindow(WinData->window);
fred = Safefred;
 
Thanks for any suggestions.
 
Greg

Could you also post the WinData and fred declaration ?

 _______________________________________________
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

  • Follow-Ups:
    • Re: Possible GCC Bug?
      • From: Scott Thompson <email@hidden>
References: 
 >Possible GCC Bug? (From: "Greg Knight" <email@hidden>)

  • Prev by Date: Possible GCC Bug?
  • Next by Date: Re: Possible GCC Bug?
  • Previous by thread: Possible GCC Bug?
  • Next by thread: Re: Possible GCC Bug?
  • Index(es):
    • Date
    • Thread