NVIZ Segmentation Fault

[Markus Neteler]

Hi there,

> > My
> >last strace on NVIZ seemed to indicate it fails shortly after loading
> >the tk.tcl interface.  It appears to send an inappropriate IO request:
> >
> >access("/usr/lib/tk8.0/tk.tcl", F_OK)   = 0
> >stat("/usr/lib/tk8.0/tk.tcl", {st_mode=S_IFREG|0644, st_size=5697, ...})
> >= 0
> >open("/usr/lib/tk8.0/tk.tcl", O_RDONLY) = 7
> >fcntl(7, F_SETFD, FD_CLOEXEC)           = 0
> >ioctl(7, TCGETS, 0xbfffd8c8)            = -1 ENOTTY (Inappropriate ioctl
> >for device)
> >read(7, "# tk.tcl --\n#\n# Initialization s"..., 4096) = 4096
> >read(7, "vent add <<Clear>> <Clear>\n    }"..., 4096) = 1601
> >close(7)                                = 0
> >--- SIGSEGV (Segmentation fault) ---
> >+++ killed by SIGSEGV +++
> 
> This is also good to see - an strace on my machine looks pretty close to
> identical. I guess I need to recompile and look for any suspect messages.
> 
> 
> >I wonder if ENOTTY has any relation to UNIX 98 PTYs? Just speculatin'...
> 
> Hopefully there is an NVIZ person out there who may recognize where this is
> happening.

I am still searching for someone with programming knowledge to
fix this :-)

What I found here:

The GNU C Library
http://gnu.senet.com.au/glibc/libc_2.html

 Macro: int ENOTTY 
    Inappropriate I/O control operation, such as trying to set terminal
    modes on an ordinary file. 

Maybe this is useful to somebody. Could it be a wrong
sprintf, fprintf call somewhere in 
src.contrib/GMSL/NVIZ2.2/src/
?

Note: On some Linux boxes it works (luckily on my system).

Regards

 Markus Neteler