From: Joseph P. <j-...@no...> - 2006-09-20 20:23:19
|
Hey all, Anyone have any luck getting cr beta 4 running on OSX? It seems to build fine, but every application is segfaulting (even when using the most simple of configurations). Thanks in advance, --Joe |
From: James S. <arr...@gm...> - 2006-09-20 20:42:16
|
I probably won't be able to help you with the problem, but no one will be able to help you with the information you have given. We need a stack trace from the time of crash. This will tell us were (in which function) the crash is occurring in. Also, please tell about your setup. How many SPUs, which is crashing, and in what configuration? Which node is crashing? An application node, a server node? etc. Thank you for your time, James Steven Supancic III |
From: Joseph P. <j-...@no...> - 2006-09-20 20:55:17
|
James, I was wondering if it was a general problem since it is failing with every configuration i've tried with every demo app within chromium. From what i can tell it, is the CrAppFaker that is crashing. Everything looks normal up until after the CrAppFaker finds the system GL, AGL, CGL paths, then it prints CGLSetOption(505) a couple thousand times and then CR Debug(karmacode:4789): Dead connection (sock=7, host=karmacode), removing from pool CR Debug(karmacode:4789): Deleting client 0x112a030 (0 msgs left) CR Debug(karmacode:4789): Last client deleted - empty run queue. CR Debug(karmacode:4789): Cleaning up SPU render CR Debug(karmacode:4789): Cleaning up SPU error CR Error(karmacode:4734): "city" terminated with uncaught signal=11 (SIGSEGV) CRserver dumps: CR Debug(karmacode:4816): Accepted connection from "karmacode". CR Debug(karmacode:4816): Adding client 0x112a010 to the run queue CR Debug(karmacode:4816): Added tile: 0, 0 .. 320, 240 CR Info(karmacode:4816): Total output dimensions = (640, 240) CR Debug(karmacode:4817): Accepted connection from "karmacode". CR Debug(karmacode:4817): Adding client 0x112a010 to the run queue CR Debug(karmacode:4817): Added tile: 320, 0 .. 640, 240 CR Info(karmacode:4817): Total output dimensions = (640, 240) CR Debug(karmacode:4817): Dead connection (sock=7, host=karmacode), removing from pool CR Debug(karmacode:4817): Deleting client 0x112a010 (0 msgs left) CR Debug(karmacode:4817): Last client deleted - empty run queue. CR Debug(karmacode:4816): Dead connection (sock=7, host=karmacode), removing from pool CR Debug(karmacode:4817): Cleaning up SPU render CR Debug(karmacode:4816): Deleting client 0x112a010 (0 msgs left) CR Debug(karmacode:4816): Last client deleted - empty run queue. CR Debug(karmacode:4816): Cleaning up SPU render CR Debug(karmacode:4816): Cleaning up SPU error CR Debug(karmacode:4817): Cleaning up SPU error I've tried Mural, crdemo, dist_textures, wall, cr, and simplemural. All running off the localhost. The most simple of configuration 1 crserver, 1 appfaker has the same problem as the more complex mural configs. Also, city runs fine standalone. Hope that helps, --Joe On Sep 20, 2006, at 3:42 PM, James Supancic wrote: > I probably won't be able to help you with the problem, but no one will > be able to help you with the information you have given. > > We need a stack trace from the time of crash. This will tell us were > (in which function) the crash is occurring in. > > Also, please tell about your setup. How many SPUs, which is crashing, > and in what configuration? > > Which node is crashing? An application node, a server node? etc. > > Thank you for your time, > James Steven Supancic III > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Chromium-users mailing list > Chr...@li... > https://lists.sourceforge.net/lists/listinfo/chromium-users |
From: James S. <arr...@gm...> - 2006-09-20 21:44:54
|
My guess is that the root of the problem has something to do with CGLSetOption, further, I would guess that you may have some mutual recursion going on... The function spewing the message is CGLError CGLSetOption(CGLGlobalOption pname, long param) { // DEBUG_FUNCTION(CGLSetOption); crDebug("CGLSetOption( %i )", pname); stubInit(); return stub.wsInterface.CGLSetOption( pname, param ); } code 505 is for the option kCGLGOUseErrorHandler I am not really sure... you may try changing it to CGLError CGLSetOption(CGLGlobalOption pname, long param) { // DEBUG_FUNCTION(CGLSetOption); crDebug("CGLSetOption( %i )", pname); stubInit(); return noErr; } temporarily for the purpose of debugging. If it fixes the problem we will know a lot more about the problem. Another option might be to use GLX, don't the new Apple hosts support X11? I am not sure if GLX is supported or not... Thank you for your time, James Steven Supancic III |
From: Joseph P. <j-...@no...> - 2006-09-20 21:57:10
|
Would running under X11 just constitute using the provided X11 shell to launch applications? or is there a different setup i need to use? I'm new to the Mac end of chromium, so a little green on it's configuration. On that change, i get repeated: CR Debug(karmacode:15280): CGLChoosePixelFormat: kCGLPFADoubleBuffer CR Debug(karmacode:15280): CGLChoosePixelFormat: kCGLPFADepthSize: 12 then the segfault. Thanks again, --Joe On Sep 20, 2006, at 4:44 PM, James Supancic wrote: > My guess is that the root of the problem has something to do with > CGLSetOption, further, I would guess that you may have some mutual > recursion going on... > > The function spewing the message is > CGLError CGLSetOption(CGLGlobalOption pname, long param) { > // DEBUG_FUNCTION(CGLSetOption); > crDebug("CGLSetOption( %i )", pname); > > stubInit(); > > return stub.wsInterface.CGLSetOption( pname, param ); > } > > code 505 is for the option kCGLGOUseErrorHandler > > I am not really sure... you may try changing it to > CGLError CGLSetOption(CGLGlobalOption pname, long param) { > // DEBUG_FUNCTION(CGLSetOption); > crDebug("CGLSetOption( %i )", pname); > > stubInit(); > > return noErr; > } > > temporarily for the purpose of debugging. If it fixes the problem we > will know a lot more about the problem. > > Another option might be to use GLX, don't the new Apple hosts support > X11? I am not sure if GLX is supported or not... > > Thank you for your time, > James Steven Supancic III |
From: Joseph P. <j-...@no...> - 2006-09-21 20:47:56
|
I tried changing the GL includes to use the OSX X11 ones (Not the framework), i think the work on this is going to go deeper than a simple configuration. And it seems to be the only definition of CGLSetOption in the code, and yes it does seem to be calling it self. The same goes for the CGLChoosePixelFormat.. On nativeOpenGL it calls stub.wsInterface.CGLChoosePixelFormat, which also makes me think it's recursively calling itself. --Joe On Sep 20, 2006, at 4:57 PM, Joseph Paris wrote: > Would running under X11 just constitute using the provided X11 shell > to launch applications? or is there a different setup i need to use? > I'm new to the Mac end of chromium, so a little green on it's > configuration. > > On that change, i get repeated: > > CR Debug(karmacode:15280): CGLChoosePixelFormat: kCGLPFADoubleBuffer > CR Debug(karmacode:15280): CGLChoosePixelFormat: kCGLPFADepthSize: 12 > > then the segfault. > > Thanks again, > --Joe > > On Sep 20, 2006, at 4:44 PM, James Supancic wrote: > >> My guess is that the root of the problem has something to do with >> CGLSetOption, further, I would guess that you may have some mutual >> recursion going on... >> >> The function spewing the message is >> CGLError CGLSetOption(CGLGlobalOption pname, long param) { >> // DEBUG_FUNCTION(CGLSetOption); >> crDebug("CGLSetOption( %i )", pname); >> >> stubInit(); >> >> return stub.wsInterface.CGLSetOption( pname, param ); >> } >> >> code 505 is for the option kCGLGOUseErrorHandler >> >> I am not really sure... you may try changing it to >> CGLError CGLSetOption(CGLGlobalOption pname, long param) { >> // DEBUG_FUNCTION(CGLSetOption); >> crDebug("CGLSetOption( %i )", pname); >> >> stubInit(); >> >> return noErr; >> } >> >> temporarily for the purpose of debugging. If it fixes the problem we >> will know a lot more about the problem. >> >> Another option might be to use GLX, don't the new Apple hosts support >> X11? I am not sure if GLX is supported or not... >> >> Thank you for your time, >> James Steven Supancic III > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Chromium-users mailing list > Chr...@li... > https://lists.sourceforge.net/lists/listinfo/chromium-users |
From: Brian P. <bri...@tu...> - 2006-09-21 20:49:51
|
Does Cr 1.8 work for you on OS X? If so, try diff'ing the files under opengl_stub/ and spu_loader/ to see what might have changed between 1.8 and 1.9. -Brian |
From: Joseph P. <j-...@no...> - 2006-09-21 21:57:59
|
I can't get Cr 1.8 to build on OSX. Some GL_MAP2_VERTEX_ATTRIB undeclared build errors in pack_map.c It lists the whole lot of em. --Joe On Sep 21, 2006, at 3:49 PM, Brian Paul wrote: > > Does Cr 1.8 work for you on OS X? > > If so, try diff'ing the files under opengl_stub/ and spu_loader/ to > see what might have changed between 1.8 and 1.9. > > -Brian |
From: Brian P. <bri...@tu...> - 2006-09-21 22:03:56
|
Try copying over the include/GL/glext.h file from Cr 1.9 to 1.8. -Brian Joseph Paris wrote: > I can't get Cr 1.8 to build on OSX. Some GL_MAP2_VERTEX_ATTRIB > undeclared build errors in pack_map.c It lists the whole lot of em. > > --Joe > > > On Sep 21, 2006, at 3:49 PM, Brian Paul wrote: > > >>Does Cr 1.8 work for you on OS X? >> >>If so, try diff'ing the files under opengl_stub/ and spu_loader/ to >>see what might have changed between 1.8 and 1.9. >> >>-Brian > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Chromium-users mailing list > Chr...@li... > https://lists.sourceforge.net/lists/listinfo/chromium-users > |
From: Joseph P. <j-...@no...> - 2006-09-21 22:39:06
|
Same problem. Is there a way to disable using CGL? Since the X11 server/utils that OSX come with include GLX, it might work if i can avoid CGL all together. Open to any suggestions at this point ;-) --Joe On Sep 21, 2006, at 5:03 PM, Brian Paul wrote: > Try copying over the include/GL/glext.h file from Cr 1.9 to 1.8. > > -Brian > > Joseph Paris wrote: >> I can't get Cr 1.8 to build on OSX. Some GL_MAP2_VERTEX_ATTRIB >> undeclared build errors in pack_map.c It lists the whole lot of em. >> >> --Joe >> >> >> On Sep 21, 2006, at 3:49 PM, Brian Paul wrote: >> >> >>> Does Cr 1.8 work for you on OS X? >>> >>> If so, try diff'ing the files under opengl_stub/ and spu_loader/ to >>> see what might have changed between 1.8 and 1.9. >>> >>> -Brian >> >> >> >> --------------------------------------------------------------------- >> ---- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys -- and earn >> cash >> http://www.techsay.com/default.php? >> page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Chromium-users mailing list >> Chr...@li... >> https://lists.sourceforge.net/lists/listinfo/chromium-users >> > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Chromium-users mailing list > Chr...@li... > https://lists.sourceforge.net/lists/listinfo/chromium-users |
From: James S. <arr...@gm...> - 2006-09-20 22:51:54
|
Ok, revert that change and rebuild the server. After doing so, can you tell me what method is being called by stub.wsInterface.CGLSetOption( pname, param ) in CGLSetOption? I suspect it may be calling itself? If this is the case it may be a simple matter of changing your environment a bit to get things working? I don't have a OSX machine to test things on. I have no idea how you would configure Chromium to work with GLX on OSX. I think you would have to rebuild it for a different target? I think your Chromium is built with the Darwin target, you may have to create a new target. Thank you for your time, James Steven Supancic III |
From: Joseph P. <j-...@no...> - 2006-09-21 15:45:21
|
It definitely seems to be calling itself. And it seems to be the only definition of CGLSetOption in the code. GLX Is in osx, under the extra X11 utility install umbrella. I'm guessing a possible target using that method would look more like the Linux version with the correct dynlib stuff that Osx uses? --Joe On Sep 20, 2006, at 5:51 PM, James Supancic wrote: > Ok, revert that change and rebuild the server. > > After doing so, can you tell me what method is being called by > stub.wsInterface.CGLSetOption( pname, param ) in CGLSetOption? I > suspect it may be calling itself? If this is the case it may be a > simple matter of changing your environment a bit to get things > working? > > I don't have a OSX machine to test things on. > > I have no idea how you would configure Chromium to work with GLX on > OSX. I think you would have to rebuild it for a different target? I > think your Chromium is built with the Darwin target, you may have to > create a new target. > > Thank you for your time, > James Steven Supancic III |