[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20000103: problem with garp 2.1
- Subject: 20000103: problem with garp 2.1
- Date: Mon, 03 Jan 2000 16:15:50 -0700
Art....
It actually is something simple. It turns out that
the area files are using 3 digit years instead of 4 digit years.
Gempak is expecting either 2 digits or 4 digits.
The affected routine is $GEMPAKHOME/src/gemlib/im/imar2gm.f,
and I have placed an updated version of this routine in
~gbuddy/nawips-5.4/patches/imar2gm.f
This routine is also used by all the text interface programs which
display satellites with the SATFIL variable.
You can download this file into the $GEMPAKHOME/src/gemlib/im directory
and patch your distribution with:
cd $GEMPAKHOME/src/gemlib/im
make clean
make all
make clean
cd $GARPHOME
make all
make install
make clean
cd $GEMPAKHOME/src/programs/
make all
make install
make clean
Sorry for omitting that routine in the patch. Nsat also needs to be updated
if you use that program (but Garp basically alleviates the need). If you do,
then in $NAWIPS/nprogs/nsat/source/file.c, around line 79 should be updated
from:
sprintf(tmpdate, "%s %s 19%s", day, months[m-1], year);
to:
if(year[0] < '2')
sprintf(tmpdate, "%s %s 20%s", day, months[m-1], year);
else
sprintf(tmpdate, "%s %s 19%s", day, months[m-1], year);
Steve Chiswell
Unidata User Support
>From: "Arthur A. Person" <address@hidden>
>Organization: .
>Keywords: 200001032251.PAA17992
>Hi...
>
>I'm trying to install the update for garp to 2.1 but when I type garp and
>pick something like a satellite image down through the menus, it segment
>faults. I followed the order of the building instructions. To help
>debug, I did a truss garp to see what it was doing (last few lines):
>
>writev(3, 0xFFBE355C, 1) = 10240
>writev(3, 0xFFBE355C, 1) = 10240
>writev(3, 0xFFBE355C, 1) = 10240
>writev(3, 0xFFBE355C, 1) = 10240
>writev(3, 0xFFBE355C, 1) = 10240
>writev(3, 0xFFBE355C, 1) = 10240
>writev(3, 0xFFBE355C, 1) = 4352
>stat64("ir_upc.tbl", 0xFFBED2A0) Err#2 ENOENT
>lstat64("ir_upc.tbl", 0xFFBED2A0) Err#2 ENOENT
>stat64("ir_upc.tbl", 0xFFBED2A0) Err#2 ENOENT
>lstat64("ir_upc.tbl", 0xFFBED2A0) Err#2 ENOENT
>stat64("$GEMTBL/luts/ir_upc.tbl", 0xFFBED2A0) Err#2 ENOENT
>lstat64("$GEMTBL/luts/ir_upc.tbl", 0xFFBED2A0) Err#2 ENOENT
>stat64("/opt1/gempak/NAWIPS/gempak5.4/tables/luts/ir_upc.tbl", 0xFFBED2A0)
>= 0
>stat64("$GEMTBL/luts/ir_upc.tbl", 0xFFBED1C0) Err#2 ENOENT
>lstat64("$GEMTBL/luts/ir_upc.tbl", 0xFFBED1C0) Err#2 ENOENT
>stat64("/opt1/gempak/NAWIPS/gempak5.4/tables/luts/ir_upc.tbl", 0xFFBED1C0)
>= 0
>sigprocmask(SIG_SETMASK, 0xFFBED378, 0xFFBED388) = 0
>open64("/opt1/gempak/NAWIPS/gempak5.4/tables/luts/ir_upc.tbl", O_RDWR)
>Err#13 EA
>CCES
>sigprocmask(SIG_SETMASK, 0xFFBED388, 0x00000000) = 0
>sigprocmask(SIG_SETMASK, 0xFFBED378, 0xFFBED388) = 0
>open64("/opt1/gempak/NAWIPS/gempak5.4/tables/luts/ir_upc.tbl", O_RDONLY) =
>4
>sigprocmask(SIG_SETMASK, 0xFFBED388, 0x00000000) = 0
>fstat64(4, 0x02CDA5F8) = 0
>ioctl(4, (('m'<<8)|2), 0xFFBED380) Err#25 ENOTTY
>fstat64(4, 0xFFBED278) = 0
>fstat64(4, 0xFFBED278) = 0
>ioctl(4, TCGETA, 0xFFBED204) Err#25 ENOTTY
>fstat64(4, 0xFFBED620) = 0
>ioctl(4, TCGETA, 0xFFBED5AC) Err#25 ENOTTY
>read(4, " ! C o l o r n a m e ".., 8192) = 5303
>llseek(4, 0, SEEK_CUR) = 5303
>llseek(4, 0xFFFFFFFFFFFFEBA9, SEEK_CUR) = 96
>llseek(4, 0, SEEK_CUR) = 96
>llseek(4, 0, SEEK_CUR) = 96
>llseek(4, 0, SEEK_SET) = 0
>read(4, " ! C o l o r n a m e ".., 96) = 96
>read(4, " ".., 8192) = 5207
>read(4, 0x02CCBB04, 8192) = 0
>ioctl(4, TCGETA, 0xFFBED804) Err#25 ENOTTY
>llseek(4, 0, SEEK_CUR) = 5303
>close(4) = 0
>write(3, " Y02\005\0\0\0 4\0\0\0 n".., 2040) = 2040
>write(3, " Y02\005\0\0\0 4\0\0\0D4".., 1040) = 1040
>read(3, "01\01BC7\0\001\0\080\0\0".., 32) = 32
>read(3, "\0\0\0\0\0\0 } d\0\0\0\0".., 1024) = 1024
> Incurred fault #6, FLTBOUNDS %pc = 0xFEE36D68
> siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFF7
Received signal #11, SIGSEGV [default]
> siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFF7
> *** process killed ***
>
>
>It does this with the configuration files as shipped with garp (i.e. I
>didn't put our modifications back in yet) and I was able to make it pop up
>surface obs okay.
>
>Any ideas? I'm hoping the problem is just something simple.
>
> Thanks.
>
> Art.
>
>Arthur A. Person
>Research Assistant, System Administrator
>Penn State Department of Meteorology
>email: address@hidden, phone: 814-863-1563
>