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

20041004: LDM && pq->sxp->nalloc

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: 20041004: LDM && pq->sxp->nalloc
  • Date: Mon, 04 Oct 2004 14:01:32 -0600
Gerry,

>Date: Mon, 04 Oct 2004 14:03:28 -0500
>From: Gerry Creager n5jxs <address@hidden>
>Organization: AATLT, Texas A&M University
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20041004: LDM && pq->sxp->nalloc
> Keywords: 200410032323.i93NNCUE020408

The above message contained the following:

> I've attached the ldmd.log file, and I'm 'gdb-ing' the existing 
> corefiles.  So far:
> 
> (gdb) core-file core.8927
> Core was generated by `decoders/dcgrib2 -d 
> data/gempak/logs/dcgrib2_RUC.log -e GEMTBL=/home/gempak/GEM'.
> Program terminated with signal 6, Aborted.
> #0  0x0063e402 in ?? ()
> (gdb) core-file core.4622
> Core was generated by `rtstats -h rtstats.unidata.ucar.edu'.
> Program terminated with signal 6, Aborted.
> #0  0x0022f402 in ?? ()
> 
> In looking at the earlier runs, I've seen the same 2 apps failing 
> according to the corefiles.  Want a core or 2?

I'm interested in a stack trace from an upstream LDM that had an
assertion-failure.

Regards,
Steve Emmerson