Author Topic: MacsBug error capture  (Read 3590 times)

Offline chrisharjo

  • Poster
  • **
  • Posts: 95
    • View Profile
MacsBug error capture
« on: December 30, 2003, 06:49:24 AM »
tongue.gif I got a error from a program I downloaded called simple image. Here is what Macsbug picked up just the begining of the report, it is 8 pages long.
  MacsBug 6.6.3, Copyright Apple Computer, Inc. 1981-2000
 
PowerPC access exception at 00ADA9D0
 
  30-Dec-2003 6:23:38 AM (since boot = 43 minutes)
  Current application is “SimpleImage”
  Machine = #67 (PowerMac9500), System $0860, sysu = $01008000
  ROM version $077D, $34F2, $0001 (ROMBase $FFC00000)
  VM is off
  NIL^ = $68F168F1
  Stack space used = +269168708
 Address 00ADA9D0 is in the System heap at 00002800
 It is 000008A0 bytes into this heap block:
     Start    Length      Tag  Mstr Ptr Lock Prg  Type   ID   File      Name
  • 00ADA130 000025D4+10   R   008DA780   L      
 PowerPC 740/750 Registers

It thinks I have a PM9500 when actually I have a PM 8600 with a Sonnet G3 400mhz upgrade. This is going to be a challenge to figure out.

Offline kelly

  • TS Addict
  • *****
  • Posts: 17035
    • View Profile
    • http://
MacsBug error capture
« Reply #1 on: December 30, 2003, 08:02:50 AM »
I think it would take tacit to figure it out.  huh.gif

http://www.graphixmad.plus.com/mac_trouble...mac_errors.html

My guess is Buggy Software or some bad RAM. huh.gif

What does that Application do?

There's probably plenty of others out there. smile.gif
« Last Edit: December 30, 2003, 08:03:28 AM by kelly »
kelly
Veteran SuperUser

Offline tacit

  • TS Addict
  • *****
  • Posts: 1628
    • View Profile
    • http://www.xeromag.com/
MacsBug error capture
« Reply #2 on: December 30, 2003, 03:51:02 PM »
"PowerPC Access Exception" means the program attempted to access RAM that does not belong to it, or that it should not be accessing. This almost always indicates a programming error.

You can try to give the program more memory; low available memory might bring out the error.

Your upgrade card apparently changed your machine's unique identifier code, which is why it's being reported as a different model. Don't sweat it; that's not the only accelerator card that changes the machine model!
A whole lot about me: www.xeromag.com/franklin.html

Offline chrisharjo

  • Poster
  • **
  • Posts: 95
    • View Profile
MacsBug error capture
« Reply #3 on: December 31, 2003, 12:24:16 AM »
thanx.gif  for all the advice. I got another error and crash here is what Macsbug recorded:
 
  MacsBug 6.6.3, Copyright Apple Computer, Inc. 1981-2000
 
Bus Error at FFC75B0A _InitProcMenu+0022A
while reading word from BEEAF7DE in User data space
 
  31-Dec-2003 12:09:10 AM (since boot = 1 hour, 10 minutes)
  Current application is “Finder”
  Unable to access that address
  PC: FFC75B26
  Frame Type: B008
 Log file already open
 
  MacsBug 6.6.3, Copyright Apple Computer, Inc. 1981-2000
 
Bus Error at FFC75B0A _InitProcMenu+0022A
while reading word from BEEAF7DE in User data space
 
  31-Dec-2003 12:09:10 AM (since boot = 1 hour, 10 minutes)
  Current application is “Finder”
  Unable to access that address
  PC: FFC75B26

Starting to look like motherboard problems to me, might have to go back to my old PM 7300

Offline tacit

  • TS Addict
  • *****
  • Posts: 1628
    • View Profile
    • http://www.xeromag.com/
MacsBug error capture
« Reply #4 on: December 31, 2003, 03:12:51 PM »
A "bus error" is an error that occurs when a program tries to access memory that does not exist. For example, if you have 256MB of RAM, and a program tries to access a memory address that would be at the 356th MB of memory, you'll get a bus error.

Bus errors can be caused by bad RAM--but if you have this type of problem, it won't be with one program, it'll be with all your programs. In fact, the computer might not even boot if you have bad RAM that is causing bus errors.

It's actually remarkably easy to make a trivial programming error that results in this kind of problem. The fact that the bus error is occurring in InitProcMenu() is telling; most likely, what this means is the program is trying to do something with a menu item that does not exist or has not yet been created. (You can get access exceptions and bus errors, as a crude example, if you have five menu items under the File menu, and your program tells the computer to grey out the sixth menu item under the File menu--when it tries to find the memory address where the sixth menu item is stored, it may just come up with some random memory address, since there is no sixth menu item.)

My hunch is still a programming error with this one program, if you are not experiencing problems with your other applications.

I would recommend you send these crash logs to the program's author. Crash logs, especially crash logs that report the name of the procedure or Toolbox call where the error occurred, are worth their weight in gold to a programmer.
A whole lot about me: www.xeromag.com/franklin.html

Offline chrisharjo

  • Poster
  • **
  • Posts: 95
    • View Profile
MacsBug error capture
« Reply #5 on: January 01, 2004, 04:12:22 AM »
jawdrop.gif The errors are starting to happen at random now, Netscape 7 crashed and IE 5.1 crashed Futurepaint 2 along with Simple Image. My adaptec Toast program crashed when I opened it along with my Office 2001. I have 576megs of ram and have been pulling ram but the same problem, looking like the old motherboard is having problems. It crashed when I was down to motherboard ram and booting off my OS 8.5 cd. It crashed on the disk doctor on my Norton cd boot up.

Offline kelly

  • TS Addict
  • *****
  • Posts: 17035
    • View Profile
    • http://
MacsBug error capture
« Reply #6 on: January 01, 2004, 08:21:26 AM »
Have you done a thorough PRAM Zap?  huh.gif

Start from Cold Boot and let it run two or three times.

How about resetting the Motherboard?

Pull any added Cards, peripherals.
« Last Edit: January 01, 2004, 08:22:02 AM by kelly »
kelly
Veteran SuperUser

Offline chrisharjo

  • Poster
  • **
  • Posts: 95
    • View Profile
MacsBug error capture
« Reply #7 on: January 01, 2004, 04:14:54 PM »
clap.gif Found the problem. I did as Kelly suggested and started pulling PCI cards, starting with the ATI video card and used my adapter, Mac to VGA, and now using the internal video. I have the full 4 megs of VRAM install and have not crashed since then. also used the extensions manager and unchecked all the ATI stuff and rebooted, no problems so far. If this works I will send a report to ATI, they don't produce this card anymore but they might look into it. It is a ATI Orion Rage 2 PCI card with 16 megs of VRAM. Thanks to everyone for the suggestions.