• 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: Brady Duga <email@hidden>
  • Date: Tue, 8 Apr 2008 09:54:29 -0700

On Apr 8, 2008, at 9:31 AM, Greg Knight wrote:
 
// int fred has value 13
DisposeWindow(WinData->window);    // Carbon call
// int fred now has value 27

Wow, DisposeWindow() still exists? What a blast from the past! Anyway, I doubt this is a bug in GCC. I would guess either WinData or WinData->window is bogus. Try setting some breakpoints and see if they look reasonable.  You might also try turning on Guard Malloc. Or using Objective-C and Cocoa :)

--Brady
 _______________________________________________
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: 
 >Possible GCC Bug? (From: "Greg Knight" <email@hidden>)

  • Prev by Date: Re: Possible GCC Bug?
  • Next by Date: Re: Creating a custom "clean" target?
  • Previous by thread: Re: Using watchpoints... (was Re: Possible GCC Bug?)
  • Next by thread: Target Info: Build: Why sometimes sections of GCC settings?
  • Index(es):
    • Date
    • Thread