7 Replies Latest reply: May 6, 2012 8:38 PM by mynameismyname
mynameismyname Level 1 Level 1 (5 points)

Crashing different programs lately, mostly NEW ones that I started working with, like while setting up the prefs in ClamXav (anti-virus), or after uploading large files in iDrive-for-Mac (online backup), and couple others, are ALL DEFINED BY THIS SAME  EXC_BAD_ACCESS (0x0001)   and I'm wondering, is there something to it?

 

Here are 2 examples:

 

EXC_BAD_ACCESS (0x0001)

KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

 

 

EXC_BAD_ACCESS (0x0001)

KERN_INVALID_ADDRESS (0x0001) at 0xe800017a


G5 Dual Core 2 GHz, Mac OS X (10.4.11), 5 GB Ram
  • 1. Re: EXC_BAD_ACCESS (0x0001)
    Linc Davis Level 10 Level 10 (117,870 points)

    Launch the Console application in any of the following ways:

     

    Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

     

    In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

     

    If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.

     

    Step 1

     

    Enter the name of the crashed application or process in the Filter text field. Post the messages from the time of the last crash, if any — the text, please, not a screenshot.

     

    Step 2

     

    Still in the Console window, look under User Diagnostic Reports and System Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the contents — again, the text, not a screenshot. For privacy’s sake, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

  • 2. Re: EXC_BAD_ACCESS (0x0001)
    mynameismyname Level 1 Level 1 (5 points)

    OOOPPPSSS.... I realize I placed this discussion in the WRONG community..... I'm still on Tiger, 10.4.11.......

  • 3. Re: EXC_BAD_ACCESS (0x0001)
    MadMacs0 Level 4 Level 4 (3,725 points)

    mynameismyname wrote:

     

    Crashing different programs lately, mostly NEW ones that I started working with, like while setting up the prefs in ClamXav (anti-virus)

    Make sure you are using v2.2.1 of ClamXav as that was the last version that supported Tiger.

  • 4. Re: EXC_BAD_ACCESS (0x0001)
    mynameismyname Level 1 Level 1 (5 points)

    Yes, 2.2.1

  • 5. Re: EXC_BAD_ACCESS (0x0001)
    mynameismyname Level 1 Level 1 (5 points)

    OK, since my last post here, I did upgrade to Leopard, 10.5.8 and upgraded ClamXav too...

     

    But while doing something totally unrelated I got ClamXav crashing....  I have the FULL REPORT that I saved. But following your directions, here it is:

     

    This is from the main Console Message I found after the last crash:

     

    5/6/12 4:19:02 PM com.apple.launchd[100] ([0x0-0x15015].uk.co.markallan.clamxav.ClamXavSentry[139]) Exited abnormally: Bus error

    5/6/12 5:26:18 PM ClamXavSentry[143] All console output now going to /Users/Ami/Library/Logs/clamXav-scan.log

    5/6/12 5:26:32 PM ClamXavSentry[143] clamd not running. Now trying to launch it...

     

    5/6/12 5:27:07 PM ClamXavSentry[143] clamd launched successfully.  Continuing...

     

    5/6/12 5:27:07 PM ClamXavSentry[143] scan email files

     

    5/6/12 5:27:07 PM ClamXavSentry[143] I will delete infected files

     

    5/6/12 5:39:25 PM com.apple.launchd[90] ([0x0-0x17017].uk.co.markallan.clamxav.ClamXavSentry[143]) Exited abnormally: Bus error 

     

    Can't find any "User Diagnostic Reports" or "System Diagnostic Reports"

    BUT

     

    This is from Crash Reporter for the last one (5:39:25:

     

    Process:         ClamXavSentry [143]

    Path:            /Applications/Utilities/ClamXav/ClamXav.app/Contents/Resources/ClamXavSentry.ap p/Contents/MacOS/ClamXavSentry

    Identifier:      uk.co.markallan.clamxav.ClamXavSentry

    10  ...allan.clamxav.ClamXavSentry          0x00002840 _start + 756

    11  ...allan.clamxav.ClamXavSentry          0x00002544 start + 44

    3   ...allan.clamxav.ClamXavSentry          0x0000726c -[Throbber animateMenuForScan] + 216

    4   ...allan.clamxav.ClamXavSentry          0x00006cec -[Throbber mainLoop:] + 1856

    3   ...allan.clamxav.ClamXavSentry          0x0000a23c -[Dispatcher mainLoop:] + 216

    3   ...allan.clamxav.ClamXavSentry          0x0000b210 -[PatientScanner mainLoop:] + 168

    6   ...allan.clamxav.ClamXavSentry          0x0000b65c -[PatientScanner performScan] + 656

    7   ...allan.clamxav.ClamXavSentry          0x0000b294 -[PatientScanner mainLoop:] + 300

    4   ...allan.clamxav.ClamXavSentry          0x0000ce58 -[FSEventWatcher startWatching] + 584

    5   ...allan.clamxav.ClamXavSentry          0x0000cb80 -[FSEventWatcher mainLoop:] + 204

        0x1000 -    0x10fff +uk.co.markallan.clamxav.ClamXavSentry 2.6.5 (257) <79224114252815e524cb4ed2a9c4096a> /Applications/Utilities/ClamXav/ClamXav.app/Contents/Resources/ClamXavSentry.ap p/Contents/MacOS/ClamXavSentry

    0xc0000000 - 0xc000bfff +com.growl.growlframework 1.2.2 (1.2.2) <b66eb0053db266ee3fffff44a4f1cad1> /Applications/Utilities/ClamXav/ClamXav.app/Contents/Resources/ClamXavSentry.ap p/Contents/Frameworks/Growl.framework/Versions/A/Growl

  • 6. Re: EXC_BAD_ACCESS (0x0001)
    MadMacs0 Level 4 Level 4 (3,725 points)

    mynameismyname wrote:

     

    OK, since my last post here, I did upgrade to Leopard, 10.5.8 and upgraded ClamXav too...

     

    But while doing something totally unrelated I got ClamXav crashing....

    This is probably a known problem for a few users with ClamXavSentry v2.6.5 that has been discussed at length on the ClamXav Forum. If you go there you can read about the work-around and somebody can explain to you why it's a bad idea to allow A-V software to both scan your e-mail files and delete infected files.

  • 7. Re: EXC_BAD_ACCESS (0x0001)
    mynameismyname Level 1 Level 1 (5 points)

    Yes.... Thanks for making that note, I guess the issue is with that program, not my Mac....