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

20041005: LDM continues to crash on bigbird

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: 20041005: LDM continues to crash on bigbird
  • Date: Tue, 05 Oct 2004 08:43:55 -0600
>From: Steve Emmerson <address@hidden>
>Organization: AATLT, Texas A&M University
>Keywords: 200410032323.i93NNCUE020408

Steve,

After seeing the LDM on bigbird exit yesterday evening due to an rtstats
exit (core dump), I rebuilt the LDM specifying debug in CFLAGS ('-g').
The LDM exited again, and again there was a core file for rtstats
(as well as two others for pqact).  A gdb output from the core file
shows:

(gdb) where
#0  0x00e7c402 in ?? ()
#1  0x007e7e49 in raise () from /lib/tls/libc.so.6
#2  0x007e9872 in abort () from /lib/tls/libc.so.6
#3  0x0804cbc1 in _uassert (
    ex=0x805fd00 "pq->rlp->nalloc == pq->nalloc && pq->tqp->nalloc == 
pq->nalloc && pq->sxp->nalloc == pq->nalloc", file=0x805efb0 "pq.c", line=3985) 
at ulog.c:965
#4  0x0805a3d8 in ctl_get (pq=0x91632c0, rflags=0) at pq.c:3984
#5  0x0805c19a in pq_sequence (pq=0x91632c0, mt=TV_GT, clss=0xfeedf880, 
    ifMatch=0x8049d54 <addtostats>, otherargs=0x0) at pq.c:5077
#6  0x0804a5aa in main (ac=3, av=0xfeedf944) at rtstats.c:379

As we talked about yesterday, I rebuilt the LDM without large file
support and then deleted and remade the queue; I also got rid of debug
flag for the build.

The newly rebuilt LDM is now running on bigbird.  We will have to wait to
see if the behavior has changed.

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.