• 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
UB issue -- include order?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

UB issue -- include order?


  • Subject: UB issue -- include order?
  • From: Mark Stultz <email@hidden>
  • Date: Fri, 17 Mar 2006 14:03:10 -0600

I'm not sure that this is the proper email list, but perhaps it is.  I have
been encountering a bug in what appears to happen only on the x86 binary of
our game.  It occurs if we switch resolutions from windowed mode to
fullscreen mode.  What happens is:

I get a CFDictionary of the display mode to switch to from:

_displayMode = ::CGDisplayBestModeForParameters( kCGDirectMainDisplay, _bpp,
_width, _height, &exactMatch );

Then I error check, capture screens, and then attempt to switch:

if ( ::CGDisplaySwitchToMode( kCGDirectMainDisplay, _displayMode ) )

And it crashes with:

============================================================
OS Version:     10.4.5 (Build 8G1454)

PID:    489
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x121fffe8

Thread 0 Crashed:
0   com.mumbojumbo.core                0x0040bc62
MemoryMgr::_heapFree(MemoryBank_s*, void*, unsigned long*) + 24
(memorymgr.cpp:955)
1   com.mumbojumbo.core                0x0040bf75 MemoryMgr::free(int,
void*) + 525 (memorymgr.cpp:580)
2   com.mumbojumbo.application         0x0003f233 operator delete(void*) +
51 (allocator.h:118)
3   com.apple.AE                       0x9150c85d AEDisposeDesc + 175
4   com.apple.AE                       0x91514053 AEPutParamPtr + 79
5   com.apple.QD                       0x91764252
ConvertDisplayConfigToAERecord + 361
6   com.apple.QD                       0x917645f9
HandleDMChangedNotification + 578
7   com.apple.QD                       0x9176e6ab InternalDisplayChangedProc
+ 84
8   com.apple.QD                       0x91770138
QDDisplayChangedNotification + 2012
9   com.apple.CoreGraphics             0x90355fb0 CGSPostLocalNotification +
275
10  com.apple.CoreGraphics             0x903c41b9 notifyDatagramHandler +
259
11  com.apple.CoreGraphics             0x90394896
CGSDispatchDatagramsFromStream + 545
12  com.apple.CoreGraphics             0x9039433a snarfEvents + 299
13  com.apple.CoreGraphics             0x906f5d08 CGSPeekNextEventRecord +
126
14  com.apple.CoreGraphics             0x904ba2fa
CGSWaitThroughReconfigurationCycle + 185
15  com.apple.CoreGraphics             0x906fb45b
CGSCompleteDisplayConfigurationWithOption + 604
16  com.apple.CoreGraphics             0x90703f54 CGDisplaySwitchToMode +
428

============================================================

For some reason it is hitting our memory manager inside a clean up of an
Apple Event?  I'm not sure why it would hit our own memory manger.  I'm not
sure if this is with include path order or what is the cause.  We are
redefining new and delete and the such, but I did not think this could
affect Apple's API.  I have not encountered this on the PPC.  Any
suggestions would be great.

Mark Stultz

 _______________________________________________
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

  • Prev by Date: Google AdWords API
  • Next by Date: Re: Dependency Checking Woes - Solution not quite right
  • Previous by thread: Re: Google AdWords API
  • Next by thread: Re: UB issue -- include order?
  • Index(es):
    • Date
    • Thread