Wiki
	· Home · Frequently Asked Questions · Development · Team Guide · Direction · Status · Task Tracking · Compiling VR Juggler · Building from SVN · SVN Branches · Compiler Status edit menu

	Main
	· About · Documentation · Publications · Download · HOWTO · FAQ · Discussion Area (Wiki) · Status · Contact

	Projects
	· VR Juggler · Gadgeteer · VPR · Sonix · JCCL · Tweek · PyJuggler · VRJ.NET

	Events
	· SIGGRAPH 2004 BoF? · SIGGRAPH 2003 BoF? · Virtual Reality Course · IEEE VR 2003 Course · SC 2002 Exhibit

	Site Search

	Sponsors
	· Infiscape · VRAC · Iowa State University · SourceForge

	Link To Us

Q: Why does my application get a segmentation fault immediately when I run on IRIX?

I have a VR Juggler application that uses omniORB. omniORB uses pthreads for its internal threads. I am using the pthreads version of VR Juggler, but my application gets a segmentation fault immediately when I try to run it. There is no output printed--only the segmentation fault error message.

A: Make sure the libraries are specified in the right order when linking the application binary.

omniORB performs static initialization of pthreads data. If the pthreads library does not appear at the very end of the link line (the -lpthread option), there may be problems with the way the runtime loader resolves symbol dependencies. In your makefile or build script or whatever, make sure that the libraries are listed in order of decreasing dependencies. Typically, the VR Juggler libraries should be first, followed by graphics API libraries (Performer, OpenGL, etc.), followed by windowing system libraries, followed by low-level system libraries. Also, make sure that there are no duplications of system libraries (-lX11, -lm, -lpthread, etc.) in your link line.

Back to: LiveFaq