|
From: Jim W. <js...@bl...> - 2005-10-10 16:05:53
|
On Oct 10, 2005, at 1:53 AM, James W. Walker wrote:
> On Oct 9, 2005, at 7:50 PM, Jim Witte wrote:
>
>
>> How do I get Geom Test on MacOSX to compile? I downloaded from
>> CVS, compiled the Quesa framework itself, and then tried to run
>> Geom Test, but get a SIGBUS error.
>>
>
> Well, then, your question is not how to get it to compile, but how
> to get it to run. :-) What are you building it with, Xcode 2.1?
> Can you run it under the debugger and tell us where it crashes?
I built it with xCode 2.1.
I'm not all that good with gdb, but if I build the app and then
run it, CrashReporter gives me the following error and trace
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000006
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x9072f2f0 CFGetAllocator + 24
1 com.apple.CoreFoundation 0x9072fcac CFURLCopyFileSystemPath + 28
2 Geom Test 0x00008b6c
loadTextureFromSupportFile + 116 (Geom Test.c:632)
3 Geom Test 0x0000e7d8 App_Initialise + 208
(Geom Test.c:3578)
4 Geom Test 0x00011314 main + 48 (QutMac.c:1864)
5 Geom Test 0x00007534 _start + 348 (crt.c:272)
6 Geom Test 0x000073d4 start + 60
This is consistent across three invocations.
I ran it with the debugger, and it gave me the following trace
-- function trace:
CFGetAllowcator
CFURLCopyFileSystemPath
loadTextureFromSupportFile
App_Initialize
main
-- asm bit from where the arrow is:
0x9072f2f0 <+0024> lhz r9,6(r3)
0x9072f2f4 <+0028> addis r2,r31,4096
0x9072f2f8 <+0032> addi r2,r2,-28788
0x9072f2fc <+0036> rlwinm r0,r9,26,22,29
0x9072f300 <+0040> lwzx r0,r2,r0
0x9072f304 <+0044> lwz r2,0(r3)
0x9072f308 <+0048> cmpw cr7,r2,r0
If I run the pre-built Geom Test (which has the 'Quesa' file along
with it - I assume it's a CFM library, that works fine.
> I haven't had a problem with Geom Test crashing, though I guess
> I've usually uses builds made with CodeWarrior.
Heh. I would too - I actually prefer CW to xCode - I think it's
interface is much cleaner, it doesn't (seem) to have preferences for
absolutely everything under the sun, it might compile and link
faster.. Except that Metrowerks went ByeBye, and I lost my CW disk
(the version that runs natively under MacOSX), and don't have a v9
disk.. AARGH!
>> Also, does Quesa development just slow down during the year, or
>> is Quesa kind of a dead project for the time being..?
>
> You could say that development is sporadic. It just depends on
> when someone has the time, inspiration, and motivation to make
> improvements. Why do you ask? Naturally, if there's something
> specific you want done, the most effective course is to do it
> yourself, or hire someone to do it, rather than waiting for someone
> else to do it. That's what my company did earlier this year when
> we wanted a cartoon-style renderer for Quesa.
I'm thinking of doing some demos in Quesa and seeing if my
Computer Graphics prof will let me show them to the class. We use
raw OpenGL, so ("this is what a *real* graphics environment looks
like..")
Another thing I saw a while ago that would be interesting (though
a LOT of work I'd think) was to do the full 'HijackGL' set of
alterations. I don't know if that would have to be platform specific
or not.
Jim
|