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

[LDM #FVI-123021]: LDM Dying

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: [LDM #FVI-123021]: LDM Dying
  • Date: Thu, 01 Mar 2007 22:41:03 -0700
Derryle,

> This is a strace output from one of the ldmd processes.
> 
> write(4, "\200\0\0\30\252\323IC\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 28) = 28
> close(4)                                = 0
> munmap(0x2aae0a3000, 270336)            = 0
> close(4)                                = -1 EBADF (Bad file descriptor)
> open("/dev/tty", O_RDWR|O_NONBLOCK|O_NOCTTY) = -1 ENXIO (No such device
> or address)
> *writev(2, [{"*** glibc detected *** ", 23}, {"double free or corruption
> (out)", 31}, {": 0x", 4}, {"0000000000544360", 16}, {" ***\n", 5}], 5) = 79*
> rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
> tgkill(18010, 18010, SIGABRT)           = 0
> --- SIGABRT (Aborted) @ 0 (0) ---
> 
> Has anyone encountered this problem before?

I've never seen this before.

The only place the string "/dev/tty" appears in the LDM source-code
is in the manual page for the "pqing" utility.

What LDM process did you trace?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FVI-123021
Department: Support LDM
Priority: Normal
Status: Closed