Re: [openvrml-develop] parse-vrml97.exe crash

[Sam U. <sa...@ho...>]

Just to let you know, the 3 missing projects I reported, do actually exist.  Only their filenames
are corrupt.  After renaming them, I was able to compile all of them.

 

I noticed that all 3 pathnames stop exactly at 100 characters:

 

openvrml-0.18.6\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-environmental-effects\x3d-environmental
openvrml-0.18.6\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-event-utilities\x3d-event-utilities.vcp
openvrml-0.18.6\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-key-device-sensor\x3d-key-device-sensor

 

Very strange corruption.

 

Anyway, even with all X3D node component DLLs compiled now, pretty-print.exe still crashes.
So, I don't know what else to try.  I tried Debug and Release mode.  Both crash.


 
> From: br...@en...
> To: ope...@li...
> Date: Sat, 3 Jul 2010 21:21:51 -0400
> Subject: Re: [openvrml-develop] parse-vrml97.exe crash
> 
> On Sat, 2010-07-03 at 20:55 -0400, Sam Url wrote: 
> > >> -rw-r--r-- braden/users 4598 2009-07-04 17:20 openvrml-0.18.6/ide->>projects/Windows/VisualC9_0/OpenVRML/x3d-environmental-effects/x3d-environmental-effects.vcproj
> > 
> > 
> > Well, that's strange. This pathname is only 115 characters. Windows can support up to 260 characters for MAX_PATH:
> 
> Windows can actually support path lengths a good deal longer than that;
> but various tools impose an artificial restriction because they use an
> obsolete API.
> 
> > "openvrml-0.18.6\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-environmental-effects\x3d-environmental-effects.vcproj"
> > 
> > 
> > 
> > Length of the path should not be a problem here.
> 
> As far as Windows' limitation is concerned, it shouldn't--in theory.
> But I wonder if the path to the current working directory has any
> bearing on this.
> 
> > I also tried GnuWin32 tar and gzip commandline tools, and it still doesn't list those files.
> 
> Now that's especially interesting; because GnuWin32 tar should (I think)
> be the same codebase as Cygwin GNU tar (which is the same codebase as
> Linux GNU tar). That sort of thing makes me suspect that this might, in
> fact, be an issue of the affected programs using an (arguably
> malfunctioning) Windows POSIX API that's imposing an artificially short
> path length.
> 
> For what it's worth, I think I've decided to move the Visual C++ project
> files under the src directory in the distribution to be near their
> related source files. The main reason for not doing this in the past
> was some anticipation that lots of (possibly conflicting) project files
> might be maintained. In practice, that hasn't happened. In particular,
> there's never been sufficient interest to maintain project files for
> more than one version of Visual C++.
> 
> So I'll be making that change when migrating to Visual C++ 2010. But
> there needs to be a Boost release with a shared_mutex that works with
> that compiler before I can make an OpenVRML release with Visual C++ 2010
> project files.
> 
> -- 
> Braden McDaniel <br...@en...>
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> openvrml-develop mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openvrml-develop
 		 	   		  
_________________________________________________________________
The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4