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

[GEMPAK #PWS-938510]: nex2img segfaults

Hi Daryl,

In regards to nex2img, I'm currently working on a change to avoid segfaulting 
or stopping when it encounters a bad file such as in this case.

In regards to problems installing 5.11.4 or 5.11.1, in my previous reply to you 
I offered to help with any issues that you encountered if you could provide me 
with more information that more precisely details the problem, such as your 
make.out file.  If you could send that file back to me I'll take a look and 
we'll figure this out.

Best,

Michael James
Unidata User Support



> Hi Unidata,
> 
> Any luck with this?  I sent the bad nexrad file to my collegue at NCDC and
> he noted that:
> 
> "I looked at it a little and it seems to me that the halfword that tells
> you the 'number of halfwords' is missing, or inaccurate. "
> 
> I am not really looking for a miracle to be able to use the data from that
> file, I would like to see nex2img simply skip bad files and use the good
> files that it can.
> 
> I still can't get 5.11.4 to run on my 64 bit linux laptop and gfortran :(
> And I can't get 5.11.1 to compile to support debugging either :(
> 
> thanks!
> daryl
> 
> On Thu, 12 Feb 2009, address@hidden wrote:
> 
> > Hi,
> >
> > Let me put this request in context a bit more.  With the kind help of NCDC, 
> > I
> > am generating a conus 1km composite every 5 minutes back to the mid 1990s.
> > nex2img is segfaulting so much that I am 'missing' many composites per year.
> > For example, for the year 2000 nex2img segfaults 3,000 some times will
> > processing the year leading to many many holes in the archive.
> >
> > daryl
> >
> > On Thu, 12 Feb 2009, Unidata GEMPAK Support wrote:
> >
> >>  Hi Daryl,
> >>
> >>  I've been able to reproduce the segmentation fault with nex2img, but it
> >>  appears that the problem stems from your test case file being unreadable
> >>  (both in nex2img and gpnids).
> >>
> >>  Have you been able to process or open this file with nex2img or gpnids
> >>  before?  You mentioned that nex2img segfaults occasionally; I would guess
> >>  that when it does the NIDS file is the culprit.
> >>
> >>  Michael James
> >>  Unidata User Support
> >>
> >>
> >>
> >> >  Greetings,
> >> >
> >> >  I have been having issues with nex2img occasionally segfaulting.
> >> >  Unfortunately, I can't seem to build a devel environment such that I
> >> >  could
> >> >  diagnose what is going on. :(
> >> >
> >> >  Attached is a reproducing test case.  I'd be curious to know if you have
> >> >  any ideas on what may be up.
> >> >
> >> >  I get segfaults on RHEL4 and RHEL5 (both x86 and x86_64) with GEMPAK
> >> >  5.11.1 ... (I haven't been able to get 5.11.4 to build properly yet.  I
> >> >  have to build GEMPAK so to build nationwide 1km composites with nex2img.
> >> >  It would be nice if the default build supported this :) )
> >> >
> >> >  thanks!
> >> >  daryl
> >> >
> >> >
> >> >  --
> >> >  /**
> >> >  * Daryl Herzmann
> >> >  * Assistant Scientist -- Iowa Environmental Mesonet
> >> >  * http://mesonet.agron.iastate.edu
> >> >  */
> >> >
> >> >
> >>
> >>
> >>  Ticket Details
> >>  ===================
> >>  Ticket ID: PWS-938510
> >>  Department: Support GEMPAK
> >>  Priority: Normal
> >>  Status: Open
> >>
> >>
> >
> >
> 
> --
> /**
> * Daryl Herzmann
> * Assistant Scientist -- Iowa Environmental Mesonet
> * http://mesonet.agron.iastate.edu
> */
> 
> 


Ticket Details
===================
Ticket ID: PWS-938510
Department: Support GEMPAK
Priority: Normal
Status: Open