• 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: Help with crash log
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help with crash log


  • Subject: Re: Help with crash log
  • From: Andreas Schweizer <email@hidden>
  • Date: Mon, 27 Aug 2001 22:33:39 +0200

Hi Andy,

thanks for the help. I'll search the archives for NSZombieEnabled afterwards.

One more thing that I've found out so far is that the crashes occur only sporadically when I run the program directly, and that they occur always when the program is running under gdb. No idea why that happens -- looks like gdb is more restrictive about accessing released memory...

Thanks,
Andy


Am Montag, 27. August 2001 um 20:19 schrieb Andreas Monitzer:

On Monday, August 27, 2001, at 02:47 , Andreas Schweizer wrote:

Hi all,

can anybody please help me to interpret the crash log below?

Thread 0:
#0 0x7081ab94 in _objc_msgSend ()
#1 0x70161f08 in _CFDictionaryGetValue ()
#2 0x73dadb30 in _RemovePortFromNativeWindowMap ()
#3 0x73da5c8c in _QDUnbindPortFromNativeWindow ()
#4 0x737cc4ec in _DisposeMenuWindow__FP16OpaqueMenuHandle ()
#5 0x737cc28c in _InvalidateMenuSize__FP8MenuData ()
#6 0x737cec00 in _InvalidateMenuItems ()

My guess is that the value is released once more than it should. Maybe that value should be some menu item?
You could try that NSZombieEnabled (or something like this, search the archives)-thing.


andy
--
Discussion forthcoming.


References: 
 >Re: Help with crash log (From: Andreas Monitzer <email@hidden>)

  • Prev by Date: Re: NSTableView
  • Next by Date: Re: Carbon <-> Cocoa
  • Previous by thread: Re: Help with crash log
  • Next by thread: Re: Help with crash log
  • Index(es):
    • Date
    • Thread