[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20000923: McIDAS-X scc produces segementation violation (cont.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20000923: McIDAS-X scc produces segementation violation (cont.)
  • Date: Sat, 23 Sep 2000 10:29:19 -0600
>From: weather <address@hidden>
>Organization: NMSU/NSBF
>Keywords: 200009231141.e8NBfgb15537 McIDAS-X Sun SC5.0 MDX csetkn.for

Robert,

>That's the problem,,it got compiled with -O instead of -g.

The csetkn.for exception section was missing from mccomp.sh when I
logged on.

I changed mccomp.sh; remade mccomp; deleted csetkn.o; and then
remade mdx.k.  csetkn.o got correctly built with '-g'.  Now, all
the MDX macros should run with no segmentation violation.

I ran MDX by itself with no errors, so I feel pretty confident about
the fix:

cd ~/workdata
mdx.k T MAP=NA MDF=7
---PLOTTING DONE

SCC also works:

scc.k T USA
FILE: 132 GRID: 1
 --BEGIN CONTOURS
 --END CONTOURS

>Yes I read about the Gnome thing.  To me Gnome looks cheap
>and cheesy, I like CDE much better.  

I kinda like Gnome.  Hopefully, it will take less memory than CDE.
Plus, with a number of front line Unix vendors jumping on the bandwagon,
it is likely to get a lot better (trying to be optimistic here :-).

Later...

Tom