Perhaps this will help others running into similar issues. The "fix" was to explicitly declare as Variant: Dim currName As Variant However, data becomes corrupted such that, on the second pass through the outer loop, the EXC_BAD_ACCESS crash occurred. It worked correctly on the first pass of the outer loop. In the Sub, the variant array was then iterated using a "For Each" loop (which crashed) For outerLoopIndex=0 To 100Įxit For ' skip any others since found a site of interest :excbadaccess ExceptionEnumString:1 :kerninvalidaddress(0x0000000000000000) /: 14:23:52 +0000 Application:Microsoft Excel ApplicationID: Application:Xcel Application:圆4 Applicationversion:16. Step 4: When the document open in Excel, remember to click the Save as a button in the yellow bar above your worksheet and save the file to the desired location.
Step 3: Select the needed file and click Open. Step 2: Go to the Recover Unsaved Workbooks. The following is somewhat speculative on what was happening.Įarlier a variant array was created, populated, and passed to a subroutine. Step 1: Click File > Open > Recent Workbooks. Through some "printf" debuggging, tracked down the issue. (Experienced programmer, just unfamiliar with OSX. How might I utilize the core dump on the exception to trace the problem? Perhaps excel has a memory limit cap for macros? Is the memory page 64k on mac like it is on PC?Ĭould it be physical ram / virtual memory / swapping? (Seems too consistent to be system os related)
EXCEL 2016 FOR MAC AND EXC_BAD_ACCESS HOW TO
I'm seeking suggestions on how to go about tracking down the issue. Which can be empty in normal operation so that's handled okay) If I comment this line out, the rest of the macro runs okay (aside from the glitch of the missing data from the container. Or possibly the temporary string used in the sub-routine is the nominal culprit? Ie, it might be using a similarly named variable from another sub-routine or something wacky. Bread and butter collection use.Īnother possible suspect might be variable scope(?). In particular, it's inserting the 2nd element into the collection. So, while that may be the point of the error, I suspect it has to do with memory of the collection - eg, perhaps it's doing a realloc behind the scenes during this particular insert. (And haven't modified it from the working PC version). Nothing fancy and doing it a zillion other places as well without a problem. The error is happening when adding an element to a collection.
EXCEL 2016 FOR MAC AND EXC_BAD_ACCESS UPDATE
Latest office update installed too (14.3 I believe it was) I'm encountering the ubiquitous EXC_BAD_ACCESS error in Microsoft Office for Mac 2011 on OSX 10.7 (Lion).
0 kommentar(er)
