Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Can you decipher this console message?

Can you decipher this console message?
Thread Tools
Forum Regular
Join Date: Nov 2002
Status: Offline
Reply With Quote
Mar 31, 2003, 09:16 PM
 
I posted this in the Software forum with no response, so I'm trying my luck here.

I've used Osex once or twice with no problems but now I'm getting this weird console message every time I fire it up. Only change that I can think of that has been made are the 3 binaries I installed for ffmpegx to work (mencoder, etc.). Any idea what's going on and how I might correct it?

Here's the console message:

Date/Time: 2003-03-30 15:12:51 -0800
OS Version: 10.2.3 (Build 6G30)
Host: [computername].local.

Command: fix_prebinding
PID: 745

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000044

Thread 0 Crashed:
#0 0x000152a4 in 0x152a4
#1 0x0000c3d8 in 0xc3d8
#2 0x0000c0ec in 0xc0ec
#3 0x0000b3ac in 0xb3ac
#4 0x00007b20 in 0x7b20
#5 0x00004250 in 0x4250
#6 0x0000290c in 0x290c
#7 0x00002414 in 0x2414
#8 0x00002a2c in 0x2a2c
#9 0x90031c44 in mach_msg_server
#10 0x00002c40 in 0x2c40
#11 0x00002f48 in 0x2f48
#12 0x00002188 in 0x2188
#13 0x00002008 in 0x2008

PPC Thread State:
srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000
r0: 0x00001860 r1: 0xbffff430 r2: 0x00000000 r3: 0x0018f708
r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230
r8: 0x000016f8 r9: 0x00000004 r10: 0x00032230 r11: 0x0016df30
r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x00000043
r16: 0x000017e8 r17: 0x00002480 r18: 0x0018d390 r19: 0x00000010
r20: 0x00032234 r21: 0x000321b8 r22: 0x0018f2c0 r23: 0x00000031
r24: 0x00032230 r25: 0x016b8160 r26: 0x00032234 r27: 0x0018f6d8
r28: 0x00000034 r29: 0x00032230 r30: 0x000016f8 r31: 0x00014914
     
Mac Elite
Join Date: Apr 2002
Location: Illinois
Status: Offline
Reply With Quote
Mar 31, 2003, 10:04 PM
 
something bad was happening at the Mach level... Nothing to do with GUI stuff as far as I can tell... You need someone with more experiance coding hex, assembly, or some serious Darwin/UNIX knowledge.
     
Professional Poster
Join Date: Jan 2001
Location: Between Sydney and Melbourne
Status: Offline
Reply With Quote
Mar 31, 2003, 10:20 PM
 
Originally posted by Preciousss:
xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000
r0: 0x00001860 r1: 0xbffff430 r2: 0x00000000 r3: 0x0018f708
r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230
r8: 0x000016f8 r9: 0x00000004 r10: 0x00032230 r11: 0x0016df30
r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x00000043
r16: 0x000017e8 r17: 0x00002480 r18: 0x0018d390 r19: 0x00000010
r20: 0x00032234 r21: 0x000321b8 r22: 0x0018f2c0 r23: 0x00000031
r24: 0x00032230 r25: 0x016b8160 r26: 0x00032234 r27: 0x0018f6d8
r28: 0x00000034 r29: 0x00032230 r30: 0x000016f8 r31: 0x00014914
Looks like you were leaning on the keyboard.
     
Senior User
Join Date: Feb 2003
Location: Atlanta
Status: Offline
Reply With Quote
Mar 31, 2003, 10:39 PM
 
This kind of info is really only useful to the developer of the program.
     
eno
Banned
Join Date: Sep 2000
Location: Fightclub
Status: Offline
Reply With Quote
Mar 31, 2003, 11:53 PM
 
Originally posted by coolmacdude:
This kind of info is really only useful to the developer of the program.
And sometimes not even to him/her!
     
Forum Regular
Join Date: Nov 2002
Status: Offline
Reply With Quote
Apr 1, 2003, 12:35 AM
 
Originally posted by coolmacdude:
This kind of info is really only useful to the developer of the program.
That's the thing, I wasn't able to locate any contact information anywhere to submit a "bug" report.

Oh well. Maybe I'll try reinstalling it to see if it rights iteself.
     
Senior User
Join Date: Feb 2003
Location: Atlanta
Status: Offline
Reply With Quote
Apr 1, 2003, 01:03 AM
 
Sometimes it is helpful though. I had a program that was crashing and i submitted what was almost a carbon copy of that and a description of what i was doing to the dev and he figured out right away what the problem was.
     
Registered User
Join Date: Jan 2003
Location: California
Status: Offline
Reply With Quote
Apr 1, 2003, 02:22 AM
 
Originally posted by Preciousss:
I posted this in the Software forum with no response, so I'm trying my luck here.

I've used Osex once or twice with no problems but now I'm getting this weird console message every time I fire it up. Only change that I can think of that has been made are the 3 binaries I installed for ffmpegx to work (mencoder, etc.). Any idea what's going on and how I might correct it?

Here's the console message:

Date/Time: 2003-03-30 15:12:51 -0800
OS Version: 10.2.3 (Build 6G30)
Host: [computername].local.

Command: fix_prebinding
PID: 745

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000044

Thread 0 Crashed:
#0 0x000152a4 in 0x152a4
#1 0x0000c3d8 in 0xc3d8
#2 0x0000c0ec in 0xc0ec
#3 0x0000b3ac in 0xb3ac
#4 0x00007b20 in 0x7b20
#5 0x00004250 in 0x4250
#6 0x0000290c in 0x290c
#7 0x00002414 in 0x2414
#8 0x00002a2c in 0x2a2c
#9 0x90031c44 in mach_msg_server
#10 0x00002c40 in 0x2c40
#11 0x00002f48 in 0x2f48
#12 0x00002188 in 0x2188
#13 0x00002008 in 0x2008

PPC Thread State:
srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000
r0: 0x00001860 r1: 0xbffff430 r2: 0x00000000 r3: 0x0018f708
r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230
r8: 0x000016f8 r9: 0x00000004 r10: 0x00032230 r11: 0x0016df30
r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x00000043
r16: 0x000017e8 r17: 0x00002480 r18: 0x0018d390 r19: 0x00000010
r20: 0x00032234 r21: 0x000321b8 r22: 0x0018f2c0 r23: 0x00000031
r24: 0x00032230 r25: 0x016b8160 r26: 0x00032234 r27: 0x0018f6d8
r28: 0x00000034 r29: 0x00032230 r30: 0x000016f8 r31: 0x00014914
The problem is almost certainly due to the new binaries you installed. I am guessing you installed them either manually, or whatever way but not through the "Apple Installer".

When you install something through the Apple Installer, you must have noticed the "Optimizing" message near the end of the installation. That step does the prebinding phase - in order to make dynamically linked applications load faster, it creates prebinding hints so that dynamic symbols are not looked up every time.

Now, if you installed an application, say, "yourself", dyld, the dynamic linker, would complain when you run the application for the first time (the complaint being that the application couldn't be launched prebound). In this case, mach_init would run fix_prebinding to "fix" things.

fix_prebinding crashes are not very uncommon in 3rd party applications, and in some cases it *is* the fault of the 3rd party application.

You might find more information on your crash in the following file:

/Library/Logs/CrashReporter/fix_prebinding.crash.log

The information you have in your post is pretty generic: symbols are messed up so the trace has hex addresses for function names.

-A
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 11:11 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2