POV-Ray : Newsgroups : povray.macintosh : Any solution on failure of POV-RAY 3.6 on intel MACs? Server Time
22 Dec 2024 01:15:25 EST (-0500)
  Any solution on failure of POV-RAY 3.6 on intel MACs? (Message 1 to 10 of 10)  
From: hauskurz
Subject: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 12 Dec 2008 09:45:01
Message: <web.49427869f207ffee9774f2ea0@news.povray.org>
I really miss being able to render my figures in POV-RAY. This problem has been
reported mutliple times and the home page even states it is not a bug but an
apple problem but siggests it is some kind of configuration problem.  Any idea
of how to fix???   What is probably needed is a universal binary.  Has anyone
solved this problem? Apple is not going to rewrite the emulator.
I am getting the Pov-Ray unexpectedly quit message that everyone else is
getting.


Post a reply to this message

From: QKRS WEB
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 22 Dec 2008 20:55:00
Message: <web.495043c5c0d61039e7186a7e0@news.povray.org>
"hauskurz" <kur### [at] biochemwustledu> wrote:

> What is probably needed is a universal binary.  Has anyone
> solved this problem?

In theory, the application just needs to be tweaked with
a tool such as "Resorcerer" http://www.mathemaesthetics.com
to set the "Application (Universal)" flag.

Looking at it from "Resorcerer," the PowerPC native "cfrg" Code Fragment
resource looks right but the "carb" Carbon Direct Launch resource is set to
"0."

My hunch is that something has to be set to invoke Rosetta (the PowerPC
Emulator) when Carbon Direct Launch is called.

I'm hunting around for a working Universal Application ported from PowerPC to
open under "Resorcerer" to confirm the hunch.

All the best ... /qkrs


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 23 Dec 2008 04:05:42
Message: <4950a9e6$1@news.povray.org>
QKRS WEB wrote:
> "hauskurz" <kur### [at] biochemwustledu> wrote:
> 
>> What is probably needed is a universal binary.  Has anyone
>> solved this problem?
> 
> In theory, the application just needs to be tweaked with
> a tool such as "Resorcerer" http://www.mathemaesthetics.com
> to set the "Application (Universal)" flag.
> 
> Looking at it from "Resorcerer," the PowerPC native "cfrg" Code Fragment
> resource looks right but the "carb" Carbon Direct Launch resource is set to
> "0."
> 
> My hunch is that something has to be set to invoke Rosetta (the PowerPC
> Emulator) when Carbon Direct Launch is called.
> 
> I'm hunting around for a working Universal Application ported from PowerPC to
> open under "Resorcerer" to confirm the hunch.

POV-Ray 3.6 is not a universal application. Please see the note on the 
website. The problem is within Apple's PowerPC emulator and only occurs on 
some systems x86 systems running Mac OS X 10.4 as well as on Mac OS X 10.5.

	Thorsten, POV-Team


Post a reply to this message

From: jasonkrupert
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 17 Jan 2009 23:10:00
Message: <web.4972ab39c0d610393acceab30@news.povray.org>
I believe I also received the same problem.  I do not believe I have an abnormal
configuration of my MacBook Pro.  Not exactly sure what that would be?

Any how, here is a copy of the report that was generated (hope this helps as I
just tried to open the application and it crashed):


Process:         POV-Ray Mac 3.6 [394]
Path:            /Applications/POV-Ray 3.6/POV-Ray Mac 3.6 Folder/POV-Ray Mac
3.6
Identifier:      POV-Ray Mac 3.6
Version:         ??? (56721408)
Code Type:       PPC (Translated)
Parent Process:  launchd [63]

Date/Time:       2009-01-17 22:06:05.866 -0600
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
Crashed Thread:  0

Thread 0 Crashed:
0   translate                      0xb80bcd58 0xb8000000 + 773464
1   translate                      0xb80b7007 0xb8000000 + 749575
2   translate                      0xb80d49c0 0xb8000000 + 870848
3   translate                      0xb813ce79 spin_lock_wrapper + 1981

Thread 1:
0   ???                            0x800bc1c6 0 + 2148254150
1   ???                            0x800c39bc 0 + 2148284860
2   translate                      0xb818b6ea CallPPCFunctionAtAddressInt +
202886
3   ???                            0x800ed095 0 + 2148454549
4   ???                            0x800ecf52 0 + 2148454226

Thread 2:
0   translate                      0xb8152b34 spin_lock_wrapper + 91256
1   translate                      0xb8167dce CallPPCFunctionAtAddressInt +
57194
2   translate                      0xb80bdb8b 0xb8000000 + 777099
3   translate                      0xb80b7007 0xb8000000 + 749575
4   translate                      0xb80d49c0 0xb8000000 + 870848
5   translate                      0xb813d75f spin_lock_wrapper + 4259

Thread 3:
0   translate                      0xb8152c24 spin_lock_wrapper + 91496
1   translate                      0xb816c825 CallPPCFunctionAtAddressInt +
76225
2   translate                      0xb80bdb8b 0xb8000000 + 777099
3   translate                      0xb80b7007 0xb8000000 + 749575
4   translate                      0xb80d49c0 0xb8000000 + 870848
5   translate                      0xb813d75f spin_lock_wrapper + 4259

Thread 4:
0   translate                      0xb81529ef spin_lock_wrapper + 90931
1   translate                      0xb8183633 CallPPCFunctionAtAddressInt +
169935
2   translate                      0xb81861e2 CallPPCFunctionAtAddressInt +
181118
3   translate                      0xb80bdb8b 0xb8000000 + 777099
4   translate                      0xb80b7007 0xb8000000 + 749575
5   translate                      0xb80d49c0 0xb8000000 + 870848
6   translate                      0xb813d75f spin_lock_wrapper + 4259

Thread 5:
0   translate                      0xb80a101b 0xb8000000 + 659483
1   translate                      0xb815d27b CallPPCFunctionAtAddressInt +
13335
2   translate                      0xb816f06c CallPPCFunctionAtAddressInt +
86536
3   translate                      0xb80dfb0b 0xb8000000 + 916235

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00000004  ebx: 0xb80bcd30  ecx: 0x00000000  edx: 0x00000003
  edi: 0x00000004  esi: 0x80303820  ebp: 0xb7fffa08  esp: 0xb7fff9d0
   ss: 0x0000001f  efl: 0x00010206  eip: 0xb80bcd58   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x00000004

Binary Images:
0xb8000000 - 0xb81d7fe7  translate ??? (???) /usr/libexec/oah/translate

Translated Code Information:
Rosetta Version:  21.03
Args:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
/Applications/POV-Ray 3.6/POV-Ray Mac 3.6 Folder/POV-Ray Mac 3.6
Exception: EXC_BAD_ACCESS (0x0001)

Thread 0: (0xb0220ea8, 0xb816effd)
0x7ff43868: No symbol
0x7ff4744c: No symbol
0x7ff429ec: No symbol
0x7ff47394: No symbol
0x9545247c:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _PrivateMPEntryPoint + 80
0x9545247c:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _PrivateMPEntryPoint + 80
0x910c317c: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x7ff4744c  ctr: 0x91032280
r00: 0xffffffc5  r01: 0xf02afcd0  r02: 0x9546681c  r03: 0x00000000
r04: 0x00005000  r05: 0x00005000  r06: 0x00000000  r07: 0x0085fe00
r08: 0x0085fe00  r09: 0x000000ff  r10: 0x000000ff  r11: 0xa0269cc4
r12: 0x91032280  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
r20: 0x00000000  r21: 0x00000000  r22: 0x00000000  r23: 0x00000000
r24: 0x00000000  r25: 0x00000000  r26: 0x00000000  r27: 0x00000000
r28: 0x00000000  r29: 0x00879000  r30: 0x15f90d88  r31: 0xf02afd60

Thread 1: (0xb019e77c, 0xb81529ef)
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0
0x95481bc8:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _YieldToThread + 532
0x954819a4:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _YieldToAnyThread + 20
0x852d10c4: No symbol
0x95486df4:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _CooperativeThread + 348
0x910c317c: /usr/lib/libSystem.B.dylib : __pthread_body + 40

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x91039080  ctr: 0x91032150
r00: 0xffffffe1  r01: 0xf0182c90  r02: 0x00000013  r03: 0xf0182d3c
r04: 0x00000003  r05: 0x00000018  r06: 0x00000020  r07: 0x00006607
r08: 0x00000000  r09: 0x00000000  r10: 0x00000000  r11: 0xa0269694
r12: 0x91032150  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
r20: 0x00000000  r21: 0x00000000  r22: 0x00000000  r23: 0x00000018
r24: 0xf0182d3c  r25: 0x00000020  r26: 0x00006607  r27: 0x00000000
r28: 0x00000000  r29: 0x00000003  r30: 0x00000003  r31: 0x954819bc

Thread 2: (0xb011cd38, 0xb8152c24)
0x9107528c: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 1260
0x0044804c:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _CarbonOperationThreadFunc + 136
0x910c317c: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x910753d0  ctr: 0x9103d45c
r00: 0x0000014e  r01: 0xf0101a50  r02: 0xf0101a90  r03: 0x00003603
r04: 0x00003703  r05: 0x00000000  r06: 0x00000000  r07: 0x00000000
r08: 0x00000000  r09: 0x00000001  r10: 0xfffffff1  r11: 0xa026993c
r12: 0x9103d45c  r13: 0xf0101b28  r14: 0xf0101b24  r15: 0xf0101b20
r16: 0xf0101b1c  r17: 0xf0101b18  r18: 0xf0101ce8  r19: 0x00000000
r20: 0x00000000  r21: 0x00000000  r22: 0x00000000  r23: 0x00000000
r24: 0x00000000  r25: 0x00000000  r26: 0x00000000  r27: 0xa0264db4
r28: 0x0011b130  r29: 0x00819200  r30: 0x0011b0d8  r31: 0x91074db4

Thread 3: Crashed (0xb7fff9d0, 0xb80bcd58)
0x8536a3cc: No symbol
0x852d7a9c: No symbol
0x852d6830: No symbol
0x853cfd14: No symbol

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x8537380c  ctr: 0x9106d000
r00: 0x852d7a9c  r01: 0xbfffed30  r02: 0x003f1000  r03: 0x00000000
r04: 0x00000000  r05: 0x00000447  r06: 0x00000000  r07: 0x00000000
r08: 0x00000000  r09: 0xa029e830  r10: 0x000005b9  r11: 0xa091dbe8
r12: 0x9106d000  r13: 0x00000000  r14: 0x00000000  r15: 0x00000016
r16: 0x00000000  r17: 0x00000000  r18: 0x003fc530  r19: 0x003fd200
r20: 0x003fdb20  r21: 0x003fd2d0  r22: 0x003feb10  r23: 0x15daa5a0
r24: 0x00108920  r25: 0x003fa0f0  r26: 0xbffff6f4  r27: 0x003efb7c
r28: 0x00000000  r29: 0x00000000  r30: 0x00000009  r31: 0x00000000

Thread 4: (0xb009ad68, 0xb8152b34)
0x00446e34:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _BSD_watchevent + 44
0x0044bfb8:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _CarbonSelectThreadFunc + 204
0x910c317c: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x00446ea0  ctr: 0x910876c0
r00: 0x00000000  r01: 0xf0080d60  r02: 0x00464010  r03: 0x000000e8
r04: 0xf0080e34  r05: 0x00000000  r06: 0x00000000  r07: 0x01000000
r08: 0x00000000  r09: 0x01000000  r10: 0x00000000  r11: 0x0046442c
r12: 0x910876c0  r13: 0x00464010  r14: 0x00000000  r15: 0x00464010
r16: 0x00464008  r17: 0xf0080e18  r18: 0x0046befc  r19: 0xf0080e0c
r20: 0xf0080dfc  r21: 0xf0080e08  r22: 0xf0080e34  r23: 0x00000000
r24: 0x0046befc  r25: 0x00464010  r26: 0x00000000  r27: 0xf0080e04
r28: 0xf0080e34  r29: 0x00000000  r30: 0x00464010  r31: 0x0044befc


Post a reply to this message

From: triple r
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 18 Jan 2009 00:00:00
Message: <web.4972b680c0d61039ef2b9ba40@news.povray.org>
"jasonkrupert" <jas### [at] yahoocom> wrote:

> Identifier:      POV-Ray Mac 3.6
> Version:         ??? (56721408)
> Code Type:       PPC (Translated)
> Parent Process:  launchd [63]

> Translated Code Information:
> Rosetta Version:  21.03

Sorry in advance that I can't offer a solution.  Also, I suppose you can't
benchmark something that won't run, but it might be better (if you care about
speed) to run it natively by compiling the unix version yourself.  I found this
very simple to do, and it looks like Rosetta performance is about 50% that of
native performance.  I'm no expert on this, but only took a quick look at the
following:

http://www.geekpatrol.ca/2006/02/rosetta-performance/

I could be completely wrong about performance, but this seems reasonable, even
pretty good.

 - Ricky


Post a reply to this message

From: jasonkrupert
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 18 Jan 2009 16:00:01
Message: <web.4973974ec0d610393acceab30@news.povray.org>
"triple_r" <nomail@nomail> wrote:
> "jasonkrupert" <jas### [at] yahoocom> wrote:
>
> > Identifier:      POV-Ray Mac 3.6
> > Version:         ??? (56721408)
> > Code Type:       PPC (Translated)
> > Parent Process:  launchd [63]
>
> > Translated Code Information:
> > Rosetta Version:  21.03
>
> Sorry in advance that I can't offer a solution.  Also, I suppose you can't
> benchmark something that won't run, but it might be better (if you care about
> speed) to run it natively by compiling the unix version yourself.  I found this
> very simple to do, and it looks like Rosetta performance is about 50% that of
> native performance.  I'm no expert on this, but only took a quick look at the
> following:
>
> http://www.geekpatrol.ca/2006/02/rosetta-performance/
>
> I could be completely wrong about performance, but this seems reasonable, even
> pretty good.
>
>  - Ricky

Triple R - Thank you for your follow-up.  What are you suggesting?

Are you suggesting to try to recompile POVRay on the OS 10.5 Intel machine and
see if it works?

Has this been tried successfully before?

Thanks.


Post a reply to this message

From: triple r
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 26 Jan 2009 13:25:00
Message: <web.497dff31c0d61039ef2b9ba40@news.povray.org>
"jasonkrupert" <jas### [at] yahoocom> wrote:

> Triple R - Thank you for your follow-up.  What are you suggesting?
>
> Are you suggesting to try to recompile POVRay on the OS 10.5 Intel machine and
> see if it works?
>
> Has this been tried successfully before?

Oops.  Sorry for such a delay.  I didn't notice the reply.  My advice though, is
that if you take the "Unix / Linux / Generic Source Code" from the download page
and compile it through the OS X terminal, you should have no problems.  I also
thought it would be interesting to compare something likePOV-Ray natively
compiled and run through Rosetta, just to see the difference in performance,
except the old version doesn't seem to run on all computers.

 - Ricky


Post a reply to this message

From: Sterling Garwood
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 20 Aug 2009 22:05:00
Message: <web.4a8e0001c0d610395aea61a70@news.povray.org>
"hauskurz" <kur### [at] biochemwustledu> wrote:
> I really miss being able to render my figures in POV-RAY. This problem has been
> reported mutliple times and the home page even states it is not a bug but an
> apple problem but siggests it is some kind of configuration problem.  Any idea
> of how to fix???   What is probably needed is a universal binary.  Has anyone
> solved this problem? Apple is not going to rewrite the emulator.
> I am getting the Pov-Ray unexpectedly quit message that everyone else is
> getting.

I may have a fix from Apple .... and I have delta sources ... who do I send them
to?


Post a reply to this message

From: Sterling Garwood
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 20 Aug 2009 22:05:01
Message: <web.4a8e0032c0d610395aea61a70@news.povray.org>
"triple_r" <nomail@nomail> wrote:
> "jasonkrupert" <jas### [at] yahoocom> wrote:
>
> > Triple R - Thank you for your follow-up.  What are you suggesting?
> >
> > Are you suggesting to try to recompile POVRay on the OS 10.5 Intel machine and
> > see if it works?
> >
> > Has this been tried successfully before?
>
> Oops.  Sorry for such a delay.  I didn't notice the reply.  My advice though, is
> that if you take the "Unix / Linux / Generic Source Code" from the download page
> and compile it through the OS X terminal, you should have no problems.  I also
> thought it would be interesting to compare something likePOV-Ray natively
> compiled and run through Rosetta, just to see the difference in performance,
> except the old version doesn't seem to run on all computers.
>
>  - Ricky

I got a fix from Apple ... with delta source ... to whom do I send it?


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Any solution on failure of POV-RAY 3.6 on intel MACs?
Date: 21 Aug 2009 03:09:38
Message: <4a8e4832$1@news.povray.org>
Sterling Garwood wrote:
> "hauskurz" <kur### [at] biochemwustledu> wrote:
>> I really miss being able to render my figures in POV-RAY. This problem has been
>> reported mutliple times and the home page even states it is not a bug but an
>> apple problem but siggests it is some kind of configuration problem.  Any idea
>> of how to fix???   What is probably needed is a universal binary.  Has anyone
>> solved this problem? Apple is not going to rewrite the emulator.
>> I am getting the Pov-Ray unexpectedly quit message that everyone else is
>> getting.
> 
> I may have a fix from Apple .... and I have delta sources ... who do I send them
> to?

tho### [at] povrayorg please.

Thanks,

	Thorsten, POV-Team


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.