A Google for "EXC_BAD_ACCESS (SIGBUS)"
Brought up many programs refusing to start with the error.
This Apple Discussion seems to indicate that a System Update is needed.
Download the COMBO 10.6.8 updater and run it. http://support.apple.com/kb/DL1399
Backup your data BEFORE doing this.
I ran the updater and the problem wasn't fixed.
I can add that ver.12 worked fine, as I downloaded it as a trial, before trying the updater.
I also created a test account and ver.11 works fine with that account.
I haven't d'loaded any new s'ware recently so I'm stumped as to what file is causing the problem as it's only in my main user account.
I might need to do an "Archive & Install" but would rather put that off till all other options have been considered.
If the problem is only in your main account, the most common problem is a damaged preference file (plist)
In your user > Library > Preferences find the Filemaker.com plists and move to desktop - without FMP running - emmediately restart.
Dim possibility you have a plugin or font or font cache that could cause this.
Reinstalls almost never remove the old plists. Nor does a system update.
Removing the pref file for filemaker was actually one of the 1st fixes I tried.
I neglected to mention that. My bad.
In any event, I found a solution!!!
I reinstalled Snow Leopard from the original disk that came with the MacBook and then ran the updater.
Voila! She's fixed! Damn if I'll ever know which file got corrupted but in the final analysis it's academic.
Thanks for your kind help.
One of my favorite humor pieces - contains bad language
The link contains a bad word Google "site:theonion.com sony-releases-new-stupid-piece"
I seen cases where "repairing user account permissions" resolved the problem. Since FMP 11 seemed to work fine from a new account and re-installing fixed the problem, I would guess that there was an issue with those account settings that was repaired by your re-install Could be something else. We all work with "mysterious black boxes" in computer land--we only see what goes in and comes out--not what get's done to the input while inside the box.
Arrgh!!! It's back! Worked fine this morning now this a'noon it started up with the same problem from yesterday.
Looks like it's time to move up to ver.12 but before I buy, I'm going to run out the trial just to make sure it's stable.
Gotta love these little black boxes. Ya just never know what they're going to get up to next.