Hi Preet, The osg::notify system isn't related to handling of std exceptions except where some specific code might catch an exception and report the output to osg::notify. This means that upping the notify level won't effect how exceptions are handled.
The best thing to do is run a debugger and the look at the stack trace where the application crashes. Robert. On 31 May 2012 07:57, Preet <[email protected]> wrote: > Hiya, > > I'm trying to debug a std::bad_alloc() exception from osg that doesn't > product any other output. I can't set environment variables, so I > tried: > osg::setNotifyLevel(osg::DEBUG_INFO); > > This still doesn't give me any output. The system I'm on dumps stdout > and stderr to a log file in a specific directory and since Notify.cpp > dumps to both of those it seems like I should be seeing something, but > I'm not. However, I do get statements like "std::cout << "Hello" << > std::endl" outputted as expected when used in my application (just not > from osg). Am I missing something obvious? > > Preet > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
