Operating System - HP-UX
1834089 Members
2665 Online
110063 Solutions
New Discussion

/usr/lib/dld.sl: Call to mmap() failed

 
SOLVED
Go to solution
j773303
Super Advisor

/usr/lib/dld.sl: Call to mmap() failed

The error message as below, does anyone know how to troubleshoot the root cause.

/usr/lib/dld.sl: Call to mmap() failed - BSS /pj/grapher/lib/libgraph.sl
/usr/lib/dld.sl: Not enough space
sh: 25781 Abort(coredump)
Hero
4 REPLIES 4
Bill McNAMARA_1
Honored Contributor

Re: /usr/lib/dld.sl: Call to mmap() failed

you can get a stack trace from the core with the GNU debugger: http://www.hp.com/go/developers
but pretty soon you need source code to make much headway..

file core
what core
to find out what binary cored.

It's potentially kernel params forcing limiting the apps resources or some bug in the application or dependent libraries. Usually a system patch update will fix (or break!) this..

Later,
Bill
It works for me (tm)
Umapathy S
Honored Contributor

Re: /usr/lib/dld.sl: Call to mmap() failed

In addition to what Bill has said.

Not enough space may sometimes indicate lack of swap space also. Please check that.

HTH
Umapathy
Arise Awake and Stop NOT till the goal is Reached!
Cheryl Griffin
Honored Contributor
Solution

Re: /usr/lib/dld.sl: Call to mmap() failed

Check your access to /pj/grapher/lib/libgraph.sl. The program which your ran is referencing this library. If you do not have access to it, either permissions/owner/group, or it does not exist, or your PATH is not set right you will get this same sort of message. It looks like memory, but actually its a problem with the library.

Your PATH variable might not just be PATH, but it could be SHLIB_PATH, etc. depending on what your application needs.
"Downtime is a Crime."
vasundhara
Frequent Advisor

Re: /usr/lib/dld.sl: Call to mmap() failed

Hi,

It may be because you do not have enough free space. check with "bdf" command.

CPU is occupied with some other processes. Check the cpu usage by executing "top" command. If any process is taking full utilisation of cpu, there is a chance that you get this error.

If everything is fine, restart the system so that it clears some amount of memory.

Regards
VJ.