Excel crashes on deleting a number

B

Bernhard

Version: 2008
Operating System: Mac OS X 10.6 (Snow Leopard)
Processor: Intel

I have been using a proprietary budget system, which now crashes upon deleting/incerting a number in a specific cell. I cannot figure out what is happening and would somebody please check the crashreport as enclosed to give me a clue. The Excel-File consist of 20+ linked sheets.

The Crashreport:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-09-30 15:25:45 +0200
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.2.0.090605
Crashed Module Name: Microsoft Excel
Crashed Module Version: 12.2.0.090605
Crashed Module Offset: 0x001630c0
Blame Module Name: Microsoft Excel
Blame Module Version: 12.2.0.090605
Blame Module Offset: 0x001630c0
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x001640c0 in __mh_execute_header + 0x001630C0 (Microsoft Excel + 0x001630c0)
# 2 0x0016c64f in __mh_execute_header + 0x0016B64F (Microsoft Excel + 0x0016b64f)
# 3 0x002e7439 in __mh_execute_header + 0x002E6439 (Microsoft Excel + 0x002e6439)
# 4 0x002e7b20 in __mh_execute_header + 0x002E6B20 (Microsoft Excel + 0x002e6b20)
# 5 0x002e7c73 in __mh_execute_header + 0x002E6C73 (Microsoft Excel + 0x002e6c73)
# 6 0x00293419 in __mh_execute_header + 0x00292419 (Microsoft Excel + 0x00292419)
# 7 0x002110b6 in __mh_execute_header + 0x002100B6 (Microsoft Excel + 0x002100b6)
# 8 0x002131fb in __mh_execute_header + 0x002121FB (Microsoft Excel + 0x002121fb)
# 9 0x001cd2f0 in __mh_execute_header + 0x001CC2F0 (Microsoft Excel + 0x001cc2f0)
# 10 0x001cd456 in __mh_execute_header + 0x001CC456 (Microsoft Excel + 0x001cc456)
# 11 0x0063c4a2 in __mh_execute_header + 0x0063B4A2 (Microsoft Excel + 0x0063b4a2)
# 12 0x0063c9e2 in __mh_execute_header + 0x0063B9E2 (Microsoft Excel + 0x0063b9e2)
# 13 0x0063cd2d in __mh_execute_header + 0x0063BD2D (Microsoft Excel + 0x0063bd2d)
# 14 0x00a3f439 in __mh_execute_header + 0x00A3E439 (Microsoft Excel + 0x00a3e439)
# 15 0x00a3f53c in __mh_execute_header + 0x00A3E53C (Microsoft Excel + 0x00a3e53c)
# 16 0x00a417be in __mh_execute_header + 0x00A407BE (Microsoft Excel + 0x00a407be)
# 17 0x015132bc in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x000001DE (MicrosoftComponentPlugin + 0x0009c2bc)
# 18 0x93e28129 in .objc_class_name_IMKInkInputSession + 0x93AE37D1 (HIToolbox + 0x00008129)
# 19 0x93e273f0 in .objc_class_name_IMKInkInputSession + 0x93AE2A98 (HIToolbox + 0x000073f0)
# 20 0x93e49a81 in .objc_class_name_IMKInkInputSession + 0x93B05129 (HIToolbox + 0x00029a81)
# 21 0x93e5b8bf in .objc_class_name_IMKInkInputSession + 0x93B16F67 (HIToolbox + 0x0003b8bf)
# 22 0x93e2857a in .objc_class_name_IMKInkInputSession + 0x93AE3C22 (HIToolbox + 0x0000857a)
# 23 0x93e273f0 in .objc_class_name_IMKInkInputSession + 0x93AE2A98 (HIToolbox + 0x000073f0)
# 24 0x93e49a81 in .objc_class_name_IMKInkInputSession + 0x93B05129 (HIToolbox + 0x00029a81)
# 25 0x93eab952 in .objc_class_name_IMKInkInputSession + 0x93B66FFA (HIToolbox + 0x0008b952)
# 26 0x93eab2cf in .objc_class_name_IMKInkInputSession + 0x93B66977 (HIToolbox + 0x0008b2cf)
# 27 0x93eaaed9 in .objc_class_name_IMKInkInputSession + 0x93B66581 (HIToolbox + 0x0008aed9)
# 28 0x93e9bede in .objc_class_name_IMKInkInputSession + 0x93B57586 (HIToolbox + 0x0007bede)
# 29 0x93ee967f in .objc_class_name_IMKInkInputSession + 0x93BA4D27 (HIToolbox + 0x000c967f)
# 30 0x93e23eae in .objc_class_name_IMKInkInputSession + 0x93ADF556 (HIToolbox + 0x00003eae)
# 31 0x93e28129 in .objc_class_name_IMKInkInputSession + 0x93AE37D1 (HIToolbox + 0x00008129)
# 32 0x93e273f0 in .objc_class_name_IMKInkInputSession + 0x93AE2A98 (HIToolbox + 0x000073f0)
# 33 0x93e2724f in .objc_class_name_IMKInkInputSession + 0x93AE28F7 (HIToolbox + 0x0000724f)
# 34 0x93e5b7f3 in .objc_class_name_IMKInkInputSession + 0x93B16E9B (HIToolbox + 0x0003b7f3)
# 35 0x93
 
P

Pat McMillan

I will be happy to take a look at this. Could you please copy/paste the
entire crash log into an email message and send it directly to me at
(e-mail address removed)? If it's possible to send me that actual file (or a
stripped down version of it that still causes the problem) that would even
be better.

Thanks,

Pat
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top