Hi Robert, According to my employers OSG had never been installed on that particular machine before installing 2.8.3. However, the program was originally written for 1.2.0 on another computer and it and its Makefile have been directly copied to the new machine (where I would have to update the code to account for for example the missing osgProducer). How could I control if their recollection of events is correct or if there are any 1.2.0 parts on that machine?
The stacktrace after execution was: > #0 0x00000001 in ?? () > #1 0xb649378c in OSGReaderWriter::readNode () from > /usr/local/lib/osgPlugins-2.8.3/osgdb_osg.so > #2 0xb7c88a3c in osgDB::Registry::ReadNodeFunctor::doRead () from > /usr/local/lib/libosgDB.so.65 > #3 0xb7c7e3a2 in osgDB::Registry::read () from /usr/local/lib/libosgDB.so.65 > #4 0xb7c80527 in osgDB::Registry::readImplementation () from > /usr/local/lib/libosgDB.so.65 > #5 0xb7c84a92 in osgDB::Registry::readNodeImplementation () from > /usr/local/lib/libosgDB.so.65 > #6 0xb7c5fb99 in osgDB::readNodeFile () from /usr/local/lib/libosgDB.so.65 > #7 0x0804aded in osgDB::readNodeFile (filename=@0xbf9b7298) at > /usr/local/include/osgDB/ReadFile:106 > #8 0x0804ac29 in main () at main.cc:77 Cheers, Mark robertosfield wrote: > Hi Mark, > > On 16 March 2012 10:13, Mark Green <> wrote: > > > Ah this looks like it might be it, using that ldd command shows that " > > libosgDB.so.65 => /usr/local/lib/libosgDB.so.65 (0xb7c21000)" is being > > build, while the execution shows that > > "/usr/local/lib/osgPlugins-2.8.3/osgdb_osg.so" is being found. > > > > The Makefile which was created/generated by someone else had been left > > untouched by me since compiling and executing went fine. It currently looks > > like this (I added the "/osgPlugins-2.8.3" part just now, hoping that it > > would fix it, but the same error is given, ldd doesn't give different > > results either). > > > > > > Is there any chance you have a mixed OSG version on the system? > > As a general note, I'd recommend moving to 3.0.1 rather than 2.8.3, > API wise it should be close enough that it should primarily just be a > recompile against the newer version of the OSG. > > One the stack trace front the quickest tool to use would be to run > your application with the gnu debugger gdb, i.e. > > gdb osgviewer > > > run cow.osg > > > > To list the stack trace simply type "where" into the gdb console. > There are IDE's available tool, personally I haven't required much > more than gdb over the last decade. Prior to using gdb I used to use > VisualStudio under Windows and CaseVision under IRIX, but in the end > found them constraining and awkward to fit with the way I've found > most productive. Another tool that is very useful is valgrind for > tracking memory and threading issues. Editing wise I use KDE's text > editor Kate. > > Robert. > > > Robert. > _______________________________________________ > osg-users mailing list > > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > ------------------ > Post generated by Mail2Forum ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=46343#46343 _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
