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

[LDM #LLJ-686820]: Segfault in pqact with pipe -metadata

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 #LLJ-686820]: Segfault in pqact with pipe -metadata
  • Date: Tue, 06 Jan 2009 13:56:58 -0700
Chuck,

What a great bug!  Thanks for sending this in.

I'll be fixed in the next release.

> I think I found a minor bug in pqact in the new -metadata option to the
> pipe action.  When it tries to write a dummyprod, it segfaults.  I'm
> thinking it's trying to output something that doesn't exist in a
> dummyprod.
> 
> When I did a: (sorry about the word wrap)
> 
> ANY   (.*)
> PIPE  -close -metadata /home/kmh/area2grid/vers1/pipe_test
> 
> I got a segfault in pqact.  If I change it to:
> 
> ANY   ^pnga2area(.*)
> PIPE  -close -metadata /home/kmh/area2grid/vers1/pipe_test
> 
> it works fine.
> 
> Here is a back trace from one of the core files:
> 
> ---
> 
> gdb bin/pqact core.3687
> GNU gdb Red Hat Linux (6.6-45.fc8rh)
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and
> you are welcome to change it and/or distribute copies of it under
> certain conditions. Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details. This GDB was configured as "x86_64-redhat-linux-gnu"...
> (no debugging symbols found)
> Using host libthread_db library "/lib64/libthread_db.so.1".
> 
> warning: Can't read pathname for load map: Input/output error.
> Reading symbols from /lib64/libm.so.6...(no debugging symbols
> found)...done. Loaded symbols for /lib64/libm.so.6
> Reading symbols from /usr/lib64/libgdbm.so.2...(no debugging symbols
> found)...done. Loaded symbols for /usr/lib64/libgdbm.so.2
> Reading symbols from /lib64/libc.so.6...(no debugging symbols
> found)...done. Loaded symbols for /lib64/libc.so.6
> Reading symbols from /lib64/ld-linux-x86-64.so.2...
> (no debugging symbols found)...done.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> (no debugging symbols found)
> Core was generated by `pqact'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x0000000000403d3b in pipe_out ()
> (gdb) bt
> #0  0x0000000000403d3b in pipe_out ()
> #1  0x00000000004045ff in pipe_prodput ()
> #2  0x0000000000405a6f in processProduct ()
> #3  0x0000000000405b61 in dummyprod ()
> #4  0x0000000000407530 in main ()
> Missing separate debuginfos, use: debuginfo-install gdbm.x86_64
> glibc.x86_64 (gdb)
> 
> ---
> 
> I figured I'd give you a quick note to let you know about this.  Hopefully 
> you can reproduce it.  It's doing what I need it to do for now, so it's not a 
> high priority, but I figured you might want to fix it for the next version.
> 
> Feel free to let me know if you have any questions or need any additional 
> information.
> 
> Chuck

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: LLJ-686820
Department: Support LDM
Priority: Normal
Status: Closed