Hello Michael,
Michael Schwier wrote:
> Hi Carsten,
>
> i did this in the main to get the debug out:
> osgLog().setLogLevel(LOG_DEBUG,true);
from the log below I guess you call this after osgInit. This is,
unfortunately, too late, as the stuff I'd like to take a look at is
printed during osgInit. Please try moving the above line before osgInit
(I think this is safe) or use the environment variable (or did you try
that and it did not work ?)
Thanks,
Carsten
> i hope that was ok so far. unfortunateley i don't get anything besides:
>
> [Session started at 2007-05-15 16:35:02 +0200.]
> WARNING: Window::getFunctionByName: Couldn't get function
> 'glBindFramebufferEXT' for Window 0x7b7f298.
> WARNING: Window::getFunctionByName: Couldn't get function
> 'glFramebufferTexture2DEXT' for Window 0x7b7f298.
> WARNING: Window::getFunctionByName: Couldn't get function
> 'glCheckFramebufferStatusEXT' for Window 0x7b7f298.
> WARNING: Window::getFunctionByName: Couldn't get function
> 'glDrawBuffers' for Window 0x7b7f298.
> WARNING: Window::getFunctionByName: Couldn't get function
> 'glDeleteFramebuffersEXT' for Window 0x7b7f298.
> WARNING: Window::getFunctionByName: Couldn't get function
> 'glActiveTexture' for Window 0x7b7f298.
> WARNING: Window::getFunctionByName: Couldn't get function
> 'glMultiTexCoord2f' for Window 0x7b7f298.
> AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
>
> The "AHHH" indicates that I have a NullFC after creating the
> GeoPTypesPtr. The warnings are a complete different problem and should
> have nothing to do with the creation of the geometry node :-/ I guess
> this is not what you expected. I am running with the debug libs of OSG,
> though I am sometimes not sure if xCode isn't tricking me (well the path
> points only to the debug libs and the libraries i added are also debug).
>
> Michael
>
>
> Am 14.05.2007 um 19:02 schrieb Carsten Neumann:
>
>> Hello Michael,
>>
>> Michael Schwier wrote:
>>> I was trying to debug the code but the xCode Debugger (wich is actually
>>> gnu's gdb as far as i know) gives me a hard time. It seems to depend
>>> more on luck if it shows me a code line that is actually processed,
>>> never saw such a bad debugger ... well still it might be me doing
>>> something wrong, but i just don't get into really debugging the code, so
>>> I don't know whats happening down in the create() :-/ But I'll keep
>>> trying ...
>>
>> as Marcus already mentioned, this looks like there might be a problem
>> with the prototypes. If you are using debug libs, can you set the
>> environment variable OSG_LOG_LEVEL to DEBUG and capture the output to a
>> file. The startup logging might give some clue. The file will probably
>> be huge, so it might be necessary to compress it or you won't be able to
>> send it to the list -- or you can send it to me privately:
>> carsten_neumann AT gmx DOT net
>>
>> Thanks,
>> Carsten
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Opensg-users mailing list
>> Opensg-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/opensg-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
