Re: [openvrml-develop] How to debug openvrml? (packaging problem for gentoo linux)

[Braden M. <br...@en...>]

On Sun, 2009-10-18 at 19:09 +0200, Andreas K. Huettel wrote: 
> Am Sonntag 18 Oktober 2009 08:10:02 schrieb Braden McDaniel:
> 
> > I can reproduce this.  Before I can run into bugs in OpenVRML, there are
> > a couple of predicate issues:
> > 
> >       * If you downloaded this file and tried to load it from your local
> >         machine, the relative URIs to the Inline'd worlds would be
> >         wrong.  You'd need to download those, too.
> 
> Point taken...
> 
> > You should see an "inserted reference" when you start openvrml-player
> > (or the browser plug-in) when things are working correctly. 
> 
> Up to now there never was such a message.

Well, if openvrml-xembed never prints an "inserted reference" message to
the console, you have other problems: i.e., that means that no control
has been created for the host--which probably means that the host never
found the openvrml-xembed process.

> I tried something else, I pasted the http URL of the file into the address 
> field of the player. This is the result:
> 
> Output of xembed (in the end I killed it with ctrl-c):
> 
> huettel@pinacolada ~ $ /usr/libexec/openvrml-xembed
> ** (openvrml-xembed:6417): DEBUG: inserted reference to :1.2098
> 
> ** ERROR **: Out of memory
> aborting...
> 
> ** ERROR **: Out of memory
> aborting...
> Abgebrochen
> huettel@pinacolada ~ $
> 
> Output of the player: a few hundred :)
> 
> ** (openvrml-player:6424): CRITICAL **: 
> void<unnamed>::reset_fds(<unnamed>::CURLSource&): assertion `Invalid multi 
> handle' failed                                                                                                             

This may be a bit simpler than I thought.

I think openvrml-player starts producing these messages once
openvrml-xembed becomes unresponsive (i.e., it crashed).  That would
happen because a bug in the Collision node implementation is causing
infinite recursion and blowing out the stack.

I've now fixed that on the trunk and branches/0.18.  Can you give it a
try?

-- 
Braden McDaniel <br...@en...>