[GEMPAK #UUV-874612]: winds

If you send me stack traces like this, and you want me to repeat it to confirm 
the bug, how can I do that without knowing exactly what your input is?  I need 
an nts file or copy/paste your input.




> The new GEMPAK release 7.1.1 has the fix for this by increasing the maximum 
> grid size.
> unfortunately the fix did not work.. here is the same error again
> 
> 
> Program received signal SIGSEGV: Segmentation fault - invalid memory 
> reference.
> 
> Backtrace for this error:
> #0  0x7F22E078B667
> #1  0x7F22E078BC34
> #2  0x7F22DFD4A21F
> #3  0x4C091E in gb2_ornt at gb2ornt.c:77
> #4  0x4BFBB3 in gb2_ugem_ at gb2ugem.c:241
> #5  0x4BED8D in dp_ugb2_ at dpugb2.f:39
> #6  0x4BE766 in dm_rpkgc2_ at dmrpkgc2.c:61
> #7  0x4BE3FF in dm_rpkg_ at dmrpkg.f:84
> #8  0x4BE185 in dm_rdtr_ at dmrdtr.f:139
> #9  0x4BBC7C in gd_rdat_ at gdrdat.f:87
> #10  0x4AB655 in gd_rdatw_ at gdrdatw.f:54
> #11  0x4AB033 in cgd_rdat at cgdrdat.c:49
> #12  0x49E9B1 in dgc_nrdt_ at dgcnrdt.c:97
> #13  0x45763F in dg_robs at dgrobs.c:49
> #14  0x456600 in dg_gobs at dggobs.c:64
> #15  0x49CB66 in dg_chck at dgchck.c:529
> #16  0x45744B in dg_rgrd at dgrgrd.c:75
> #17  0x45611E in dg_gets at dggets.c:76
> #18  0x490C7B in df_mul at dfmul.c:41
> #19  0x45477F in dg_driv at dgdriv.c:203
> #20  0x44E40E in dgc_grid_ at dgcgrid.c:200
> #21  0x4343EE in dg_gridn_ at dggridn.f:78
> #22  0x40BDD3 in gdpltcf_ at gdpltcf.f:187
> #23  0x409B28 in gdpltc_ at gdpltc.c:101
> #24  0x4097B1 in gdpltb_ at gdpltb.f:278
> #25  0x407338 in gdplot at gdplot2.f:297
> Segmentation fault
> 
> 
> 
> 
> 
> 


Ticket Details
===================
Ticket ID: UUV-874612
Department: Support GEMPAK
Priority: Normal
Status: Open