• 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
Help request in debugging EXC_BAD_ACCESS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Help request in debugging EXC_BAD_ACCESS


  • Subject: Help request in debugging EXC_BAD_ACCESS
  • From: Jérôme Laurens <email@hidden>
  • Date: Thu, 24 Mar 2005 13:03:22 +0100

Hello everyone,

I am currently facing a very weird situation where I am not able to find an EXC_BAD_ACCESS bug in my document based cocoa app.
I have very serious difficulties in bug tracking and definitely need some advice.


Actually, my app crashes in a very simple situation

1 launch
2 select the menu item "open"
after a few 10th of seconds it crashes

But if I

1 launch
2 use the command shortcut for "open"

everything is ok, and it is ok also if I

1 launch
1-a scroll the main menu
1-b make the menu disappear (by clicking somewhere else)
2 select the menu item "open"

I am puzzled.

While debugging; here is what I found
- enabling NSZombie does not change anything.
- malloc debug informs me of an illegal memory access but it is not always at the same address
- the bug appears in [NSImage compositeToPoint...] while the open panel is front, so I posed as class NSImage to show the pools just before entering this method. All the objects listed by the showPools message are at 0x5 or 0x2 prefixed addresses, but malloc debug tells me the illegal address is at 0x4, where can it come from?
- If I run xcode with guard malloc option turned on, the bug simply disappears! and absolutely no malloc problem raises!
- with the bug, the open panel address is 0x2... while it is 0x5... when there is no bug
- actually my main menu contains a dozen of items not directly connected to each other. If I remove any one of these, this removes the bug.



I have managed to remove parts of my code, without breaking my code and without removing the bug. But I have come to an end where I have identified a set of disconnected methods from which I cannot remove any member without removing the bug too.


I would appreciate any kind of ideas, remarks, help, technic...

TIA

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: ANN: StepTalk for OS-X Cocoa - candidate 1
  • Next by Date: Re: NSTableView and Bindings
  • Previous by thread: Re: ANN: StepTalk for OS-X Cocoa - candidate 1
  • Next by thread: Basic Cocoa Bindings in Java
  • Index(es):
    • Date
    • Thread