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.
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to address@hidden for more info.
Pete, I didn't know you had been using the binary. If you can run my binary with your version of Linux, then try the attached version. The most likely problems are a versionitis somewhere, or the optimization by the compiler. Steve **************************************************************************** Unidata User Support UCAR Unidata Program 303 497 8643 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata WWW Service http://my.unidata.ucar.edu/content/support **************************************************************************** On Mon, 10 Oct 2005, Pete Pokrandt wrote: > > In a previous message to me, you wrote: > > > > >Pete, > >Attached is a replacement for $GARPHOME/object/displayvprof.c > > > >This fixes the use of string constants in the grid skewt. > > > >I haven't found other instances yet, but if you still have > >problems with other vertical cross sections, let me know. > > > >Steve Chiswell > > Steve, > > I compiled gemapk with the new displayvprof.c, and it has actually > made things worse. > > Garp now halts with a segfault as soon as I click on any of the > model icons (plan projection, model cross section, time/height > or vertical profile.) > > Satellite and surface/upperair data are fine. > > This is a version that I compiled on my own, as opposed to > the precompiled version of 5.8.3a that I had been using > before, so maybe this new issue is related to my recompile > rather than the new routine? > > Any ideas? I'll recompile with debugging turned on so I > can find where it's actually bombing. > > Thanks, > > Pete > > > > > -- > +>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+ > ^ Pete Pokrandt V 1447 AOSS Bldg 1225 W Dayton St^ > ^ Systems Programmer V Madison, WI 53706 ^ > ^ V address@hidden ^ > ^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^ > ^ University of Wisconsin-Madison V 262-0166 (Fax) ^ > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+ >