Constant Application gives KERN_INVALID_ADDRESS

E

emidaza

Registered
Hi there,this is my first thread i hope u can help me. I started working in a factory where they use macs to made de test to cars, things like test brakes,axis,etc. the problem is that constanstly the software they use crashes and the log gives this error

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x7838842d

Thread 4 Crashed:
0 <<00000000>> 0xfffeff20 objc_msgSend_rtp + 32
1 com.apple.HIToolbox 0x932ce2d8 EnsureParentMenu(MenuData*, OpaqueMenuRef*, MenuItemDataRef) + 56
2 com.apple.HIToolbox 0x932b9344 GetMenuItemHierarchicalMenu(MenuData*, unsigned short, MenuData**) + 384
3 com.apple.HIToolbox 0x932e36b0 GetMenuItemHierarchicalMenu + 116
4 4d.com.GigaTest.app 0x002810f0 0x1000 + 2621680
5 4d.com.GigaTest.app 0x0028111c 0x1000 + 2621724
6 4d.com.GigaTest.app 0x00286814 0x1000 + 2643988
7 4d.com.GigaTest.app 0x00286954 0x1000 + 2644308
8 4d.com.GigaTest.app 0x0028766c 0x1000 + 2647660
9 4d.com.GigaTest.app 0x00139040 0x1000 + 1278016
10 4d.com.GigaTest.app 0x00140540 0x1000 + 1307968
11 4d.com.GigaTest.app 0x00141ab0 0x1000 + 1313456
12 4d.com.GigaTest.app 0x0028ac24 0x1000 + 2661412
13 4d.com.GigaTest.app 0x00102da0 0x1000 + 1056160
14 4d.com.GigaTest.app 0x003e1bc0 0x1000 + 4066240
15 4d.com.GigaTest.app 0x0011e930 0x1000 + 1169712
16 <<00000000>> 0x02cef284 0 + 47116932

now it happens in two machines so it cant be memory, so i dont know where to start.Can u give me a clue
 
sry i forgot.the machines are conected to the macs with USB,and the macs are conected to a router. We use iMAC model powermac 8.2,with OSX
 
Hi emidaza,

Which update of Mac OS X are you running? 10.6.x, 10.5.x..?
Which version/update of the software are you running?
Which are the certified versions of Mac OS X that application GigaTest supports? It should surely list what versions of the operating system it's certified to run, and what other system requirements are there (OS, min RAM, min HD space etc)
Did that app ever run without crashing?

The crash log provides details on what happened. I'd recommend sending the crash logs to the GigaTest's developers.

The application seems to crash when hitoolbox can't give it the info in the format it can understand. Codes like 0x7838842d tell more about what was happening in the program, but to interpret those in what really happened in clear English, the crash logs should be given to the ones who made the program.
 
Man thx for the answer.That will help i will look for all that info, i know that the developers of the software must understand what happens, but im the responsable of comunicate the problems to them once a mounth and before i arrive to this factory the factory owners just send them the logs and the problems is still unsolved, thats why i ask for some clue to try to do something to get additional info to give them.
thx :)
 
Give them the crash logs of that app.
You can also find them in Console - in /Applications/Utilities
From Console, in left bar (if not showing, click on console icon to show), pick the item showing in LOG FILES > ~/Library/Logs and expand it - you will now find the crash logs for that app.
(It may be easier to grab them via Finder, again the location is ~/Library/Logs where ~ is your user home folder)

To be more effective, you can also include system logs; LOG FILES > system.log >> right click to reveal in Finder or to mail it.
I'd also recommend adding system profiler file, as that can sometimes provide more info to them. To get it, click on the upper left corner of your Mac on the apple symbol icon > About This Mac > More Info... > this opens Apple System Profiler.
In it, check that View > is in Full Profile, and then File > Save As .... in system profiler XML format.

In some programs, there is some support script that gathers both the system logs, crash logs of the app, and the system profiler logs. But for smaller applications there may not be any specific support scripts available. If that's the case for this app, you can get the developers much faster the information (such as those logs) they need to resolve the issue.

To make the the report for them more complete, I'd also suggest you add a simple step by step log for them to show how the crash occurs. Even if it's something as simple as 1. Open the X application. 2. Start to type anything in the Y bar 3. It crashes immediately.
That way they can have both the clean details in English in what is being done by the user, and the logs from the computer to show what the computer saw or thought happened.
Also don't forget to mention it happens on multiple computers - adding those files from both computers doesn't hurt. So you could add them e.g. in folders Mac1 and Mac2.
 
U are god xD.thx a lot ill do every thing,im new with mac and i was feeling lost to get info of this problem.I really apreciate ur help. bye
 
A few months full time with the Macs, and occasionally here (for finding howtos and then to help others...) and you'll be a pro too. :)
 
You must log in or register to reply here.
Back
Top