[GRASS-dev] can't get NVIZ to run

I've never had much of a need for NVIZ, though I've been meaning to look at it someday. I occassionally fire it up to try, or just to see if it runs. Every time I try to start it up recently I have problems, and possibly I've always had this problem in earlier versions of GRASS.

Right now: Mac OS X 10.4.6 Intel and PPC, GCC 4.0.1, GRASS 6.1 CVS 06-6-24 snapshot. It's my own build, not Lorenzo's binaries. TclTk 8.4.13, it IS an X11 build. GRASS built with X, opengl, but without glw and motif (those shouldn't affect nviz). I think Lorenzo has NVIZ working, so I'm not sure if it's a bug yet (and different from a few other crashing nviz bugs already reported), or just that I'm doing something wrong (in build or run stage).

I'm trying this with the spearfish6 sample. I run nviz& from the cmdline, and I get the setup window. I select a raster for elevation (elevation.10m) and run it. It shows progress in the output tab:

Loading Data
Update elev null mask
Loading Data
translating colors from fp

then crashes. The crash log has this for the crashed thread:

Command: nviz
Path: /usr/local/grass-6.1.cvs/bin/nviz
Parent: wish8.4 [7642]

Version: ??? (???)

PID: 7648
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x5c637273

Thread 0 Crashed:
0 libX11.6.dylib 0x9bd35fa1 XQueryExtension + 24
1 libGL.1.dylib 0x9be2edab glXQueryExtension + 62
2 nviz 0x000115eb Togl_CreateWindow + 56
3 com.tcltk.tklibrary 0x9ad191ad Tk_MakeWindowExist + 120
4 nviz 0x000126a3 Togl_Cmd + 1046
5 com.tcltk.tcllibrary 0x9ac181a3 TclInvokeStringCommand + 121
6 com.tcltk.tcllibrary 0x9ac1a915 TclEvalObjvInternal + 733
7 com.tcltk.tcllibrary 0x9ac3d666 TclExecuteByteCode + 3101
8 com.tcltk.tcllibrary 0x9ac4244e TclCompEvalObj + 279
9 com.tcltk.tcllibrary 0x9ac6926d TclObjInterpProc + 524
10 com.tcltk.tcllibrary 0x9ac1a915 TclEvalObjvInternal + 733
11 com.tcltk.tcllibrary 0x9ac1ac1c Tcl_EvalEx + 488
12 com.tcltk.tcllibrary 0x9ac5893a Tcl_FSEvalFile + 400
13 com.tcltk.tcllibrary 0x9ac1a915 TclEvalObjvInternal + 733
14 com.tcltk.tcllibrary 0x9ac1ac1c Tcl_EvalEx + 488
15 com.tcltk.tcllibrary 0x9ac1b03a Tcl_Eval + 42
16 nviz 0x0000cac0 Ninit + 199
17 nviz 0x00002614 NVIZ_AppInit + 210
18 com.tcltk.tklibrary 0x9acef2eb Tk_MainEx + 761
19 nviz 0x000111ca main + 97
20 nviz 0x000024ea _start + 228 (crt.c:272)
21 nviz 0x00002405 start + 41

Any ideas?
-----
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/

First Pogril: Why is life like sticking your head in a bucket filled with hyena offal?
Second Pogril: I don't know. Why IS life like sticking your head in a bucket filled with hyena offal?
First Pogril: I don't know either. Wretched, isn't it?

-HitchHiker's Guide to the Galaxy

Oops, didn't mean to send this. I was rewriting it for a bug report.

-----
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/

"History is an illusion caused by the passage of time, and time is an illusion caused by the passage of history."

- Hitchhiker's Guide to the Galaxy

I just corresponded with Lorenzo a couple of days ago and NVIZ still is not
running on Intel Macs. He can copy you the error he gets.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

From: William Kyngesburye <woklist@kyngchaos.com>
Reply-To: William Kyngesburye <kyngchaos@kyngchaos.com>
Date: Fri, 30 Jun 2006 13:09:49 -0500
To: <grass-dev@grass.itc.it>
Subject: [GRASS-dev] can't get NVIZ to run

Right now: Mac OS X 10.4.6 Intel and PPC, GCC 4.0.1, GRASS 6.1 CVS
06-6-24 snapshot. It's my own build, not Lorenzo's binaries. TclTk
8.4.13, it IS an X11 build. GRASS built with X, opengl, but without
glw and motif (those shouldn't affect nviz). I think Lorenzo has
NVIZ working, so I'm not sure if it's a bug yet (and different from a
few other crashing nviz bugs already reported), or just that I'm
doing something wrong (in build or run stage).