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

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

On Sat, 2009-10-17 at 22:28 +0200, Andreas K. Huettel wrote: 
> Hi, 
> 
> here's some more info: I downloaded the wrml file from 
> http://www.ch.ic.ac.uk/rzepa/vrml/brickmann/panel1b.wrl
> 
> > Before you start up openvrml-player or the browser plug-in, start up
> > openvrml-xembed in another terminal window.  The front end should use
> > that process instead of starting a new one.
> 
> > Do you get any console output?
> 
> Yes: from the player:
> 
> huettel@pinacolada ~ $ openvrml-player       
> 
> ** (openvrml-player:28730): CRITICAL **: 
> void<unnamed>::reset_fds(<unnamed>::CURLSource&): assertion `Invalid multi 
> handle' failed                                                                                                            
> 
> ** (openvrml-player:28730): CRITICAL **: 
> void<unnamed>::reset_fds(<unnamed>::CURLSource&): assertion `Invalid multi 
> handle' failed                                                                                                            
> 
> ** (openvrml-player:28730): CRITICAL **: 
> void<unnamed>::reset_fds(<unnamed>::CURLSource&): assertion `Invalid multi 
> handle' failed                                                                                                            
> 
> (and this repeated many times)

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. 
      * The Inline'd worlds appear to be gzipped.  This would be handled
        by libcurl (for openvrml-player) or the Web browser (for the
        browser plug-in) if the server were sending the correct
        Content-Encoding; but it doesn't appear to be doing that.

Now, once I got one of the Inline'd worlds (and commented out the rest)
and gunzipped it, I still ran into problems.

I haven't dug into this much yet, but it looks like there must be some
significant problem with Inline.  I'll investigate further.

> and from the xembed process
> 
> huettel@pinacolada ~ $ /usr/libexec/openvrml-xembed
> ** (openvrml-xembed:28728): DEBUG: erased references to :1.1885
> ** (openvrml-xembed:28728): DEBUG: erased references to :1.1889
> ** (openvrml-xembed:28728): DEBUG: erased references to :1.1889
> ** (openvrml-xembed:28728): DEBUG: erased references to :1.1890
> ** (openvrml-xembed:28728): DEBUG: erased references to :1.1891
> ** (openvrml-xembed:28728): DEBUG: erased references to :1.1879

You should see an "inserted reference" when you start openvrml-player
(or the browser plug-in) when things are working correctly.  I'm going
to assume, for the moment, that this was overlooked; because I don't
think you could have gotten as far as getting those error messages from
openvrml-player if this hadn't happened.

You might want to try a very simple VRML file to sanity check the
basics.

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