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

Re: 20050221: nmap2 seg fault/malloc problem

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: Re: 20050221: nmap2 seg fault/malloc problem
  • Date: Tue, 22 Feb 2005 14:13:50 -0500 (EST)
Steve,

On Tue, 22 Feb 2005, Unidata Support wrote:


Art,

You might check the "limit" command output to
see if the user has different restrictions on
stacksize, datasize etc than the other users.

Another possibility is that the acount is a different
group than the others and that user doesn't have read
access to the $GEMTBL files that nmap2 needs
(all the directories and fines under $NAWIPS
are packaged world readable, but that could get changed
by the user umask that unpacks the tarfile).

After those checks, it could be that the user has a table in
his/her directory that is overriding the $GEMTBL location,
and is incorrectly formatted). Can you run via gdb and determine
where the program is when the fault occurs? Have you tried launching
in a different directory as that user?
A different directory didn't work, but I then tried redefining $HOME and then it worked. There must be some table/file nmap2 is reading from the user's home directory that's bad, as you suggested. He's going to look and see if he can find it. 

                                 Thanks.

                                   Art.


Steve Chiswell
Unidata User Support




From: "Arthur A. Person" <address@hidden>
Organization: UCAR/Unidata
Keywords: 200502211649.j1LGnNv2023930



Hi...

I have one user who can't run nmap2... it gives either a segmentation
fault or a malloc failure.  Other users seem to work fine.  Can you think
of any particular problem that would prevent one user from running nmap2?
This ocurrs right at startup (window pops up, but nothing appears in it
and then it dies with the error; version 5.7.4 of gempak).

                                  Thanks.

                                    Art.
Arthur A. Person
Research Assistant, System Administrator
Penn State Department of Meteorology
email:  address@hidden, phone:  814-863-1563


--
**************************************************************************** <
Unidata User Support                                    UCAR Unidata Program <
(303)497-8643                                                  P.O. Box 3000 <
address@hidden                                   Boulder, CO 80307 <
---------------------------------------------------------------------------- <
Unidata WWW Service              http://my.unidata.ucar.edu/content/support  <
---------------------------------------------------------------------------- <
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.



Arthur A. Person
Research Assistant, System Administrator
Penn State Department of Meteorology
email:  address@hidden, phone:  814-863-1563