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

20050221: nmap2 seg fault/malloc problem

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?

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
>
--
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.