[Vis5d-users] Re: Segmentation fault, DISPLAYs, contexts and userfuncs...

Victor, 

About 1 year ago I changed jobs and much to my disappointment, I had to give 
up my continuation of development of vis5d+.  vis5d+ really needs a champion 
to lead in continuing development.  I am sure that what you see is a memory 
access to an unallocated array.  If you could take that further step and 
find and correct the problem it would be a welcomed service to the entire 
vis5d community. 

Jim 

Victor Homar writes: 

> Hi, 
> 
> I'm an old Vis5d user (nearly 7 years of use) and I'm now trying to
> migrate to the vis5d+ versions. I've downloaded the 1.2.1 and 1.3.0-beta
> packages and they "configures", and installs very well on my Linux
> RedHat8 with Nvidia OpenGL drivers (Linux 2.4.18-18.8.0smp). 
> 
> The thing is that I'm used to work with several (2 or 3) v5d files
> (contexts) and I use to "Group" them and put several contexts in the
> same DISPLAY. Now, I get a Segmentation fault when I try to "Group"
> displays (in particular when I click on the second display I want to
> group). It may be of interest that I don't get the error when I open the
> same file on the two displays (or contexts), only when I open different
> v5d files. I also get a segmentation fault when I try to put 2 contexts
> on 1 DISPLAY (through the DISPLAY buttonn at the main Vis5d+ GUI). In
> this case, even with the same v5d file opened in both DISPLAYs, I get
> the Segmentation fault. 
> 
> Another issue is the userfuncs/externf settings in vis5d+ on Linux
> machines. I know the libmain.a  was used in the old Vis5d release but
> now it looks like the external functions need it but it is not built any
> more. How can we compile external functions under Linux? 
> 
> Last thing referrs to a DATE recognition problem of vis5d when loading a 
> single-timestep files. When I open a file with only one timestep the vis5d 
> (I've noticed it in versions vis5d-1.2, vis5d+1.1, vis5d+1.2.1) does not 
> recognize the date and shows 000000 190000 instead of the correct time and 
> date. The header of the file is correct because when I append it to 
> another file (so building a multiple timesteps file), the time and date 
> are well recognized by vis5d. Have you noticed the same? Have you got a 
> patch for this bug? 
> 
> 
> Sorry if these problems have already been reported to the Vis5d lists.
> I'm trying to access to the Vis5d+ users list to see if someone has also
> found that but I get a "permission denied" error from the Source Forge
> page. I'm registered to both (devel and user) lists and to Source Forge
> also. I can  access the Vis5d+ devel list but I can't read the past
> messages of the Vis5d+ user  list. 
> 
> 
> Thanks a lot! 
> 
> Victor. 
> 
> -- 
> -----------------------------------------------------------------------
> Victor Homar Santaner						
> NRC Post-Doc
> NOAA/National Severe Storms Laboratory 
> 
> 1313 Halley Circle			  Tel: +1 (405) 579-0732
> Norman, OK  73069			  Fax: +1 (405) 366-0472
> United States				Email: Vic...@no... 
> 
>  
> 
> 
> That's the nature of research--you don't know what in hell you're doing.
> 					-- 'Doc' Edgerton
> ----------------------------------------------------------------------- 
> 
>  
> 
>  
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
> allow you to extend the highest allowed 128 bit encryption to all your 
> clients even if they use browsers that are limited to 40 bit encryption. 
> Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
> _______________________________________________
> Vis5d-devel mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/vis5d-devel