Art, > Okay, all set. The new one's running with a new core dump. Got it. Here the trace: ~: dbx bin/pqact core For information about new features see `help changes' To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc Reading pqact core file header read successfully Reading ld.so.1 Reading libm.so.2 Reading libnsl.so.1 Reading libsocket.so.1 Reading libc.so.1 Reading libdl.so.1 program terminated by signal SEGV (no mapping at the fault address) 0xfffffd7fff1244e6: realfree+0x0046: movzwq (%r12,%r14),%r8 Current function is ldmdb_put 1983 if (NULL == (new_stuff.dptr = malloc(size))) (dbx) where  realfree(0x49514e4b0a52f29e, 0x0, 0x0, 0x7, 0x1, 0x49514e4b0a0d0bc0), at 0xfffffd7fff1244e6  _malloc_unlocked(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff12406a  malloc(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff123e2f => ldmdb_put(entry = 0x45c100, keystr = 0x4412b6 "YMML", data = 0xfffffd7ff9a11f54, sz = 188U), line 1983 in "filel.c"  ldmdb_prodput(prod = 0xfffffd7fffdfef48, ac = 1, av = 0x443290, xp = 0xfffffd7ff9a11ee8, xlen = 296U), line 2073 in "filel.c"  prodAction(prod = 0xfffffd7fffdfef48, pal = 0x45cf60, xprod = 0xfffffd7ff9a11ee8, xlen = 296U), line 1121 in "palt.c"  processProduct(infop = 0xfffffd7fffdff068, datap = 0xfffffd7ff9a11f54, xprod = 0xfffffd7ff9a11ee8, xlen = 296U, otherargs = (nil)), line 1172 in "palt.c"  pq_sequence(pq = 0x45aab0, mt = TV_GT, clss = 0xfffffd7fffdffa40, ifMatch = 0x4133e0 = &processProduct(const prod_info *infop, const void *datap, void *xprod, size_t xlen, void *otherargs), otherargs = (nil)), line 6359 in "pq.c"  main(ac = 6, av = 0xfffffd7fffdffb08), line 595 in "pqact.c" Unfortunately, it's not much help. A call to malloc(375) is causing a SIGSEGV. I'm afraid I'll have to think about this. Regards, Steve Emmerson Ticket Details =================== Ticket ID: DCW-448836 Department: Support LDM Priority: Normal Status: Closed
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.