ERROR: mmap failed for dld

[GRP_2]

Hi,

On a HP-UX 10.20, our C application have crashed. We got a core file.

The result of "what core" :
>> PATCH-PHCO_20441 for 10.20; for 10.30, 11.x compatibility libc.1_ID@@/main/r10dav/libc_dav/libc_dav_cpe/9
>> /ux/core/libs/libc/shared_pa1/libc.1_ID
>> Nov 10 1999 10:53:12
>> SMART_BIND
>> 92453-07 dld dld dld.sl B.10.32 990202

Part of the result of "strings core" :
>> >> psmcasv1
>> B.10.20
>> 9000/813
>> 2004556739
>> acp.x
>> iceMiceMiceM
>> (@ NpiceM
>> iceM
>> ?PbM
>> ;dZ"@
>> /dev/console
>> proc[1] icode: execve("%F") failed, errno %E
>> Z$Revision: 92453-07 linker linker crt0.o B.10.30 980611 $
>> /usr/lib/dld.sl
>> ERROR: mmap failed for dld

The use of xdb tells us :
- "Procedure : $$dyncall_external"
- "Child died due to: bus error"

There's nothing special in the syslog.log file.

Can you help us ?

[Ruediger Noack]

I think it is a swap problem (not enough swap space). Look at your swapinfo output.
There are many threads about mmap failed here.

Ruediger

[Steven Gillard_2]

Using 'strings' on a core file is generally useless, because anything in a processes memory at the time it crashed can appear. This can include all sorts of error messages that probably have nothing to do with the fault, and in your case this is true - 'mmap failed for dld' is unlikely to have anything to do with the problem.

What you've really got is a 'bus error', which occurs when your program tries to read from a mis-aligned pointer. Basically, its a bug in your code.

First, make sure your application is compiled with -g so that full debug information is available, then get a full stack trace from xdb or some other debugger. That will show you the line of code that caused the core dump.

Regards,
Steve

[Steve Steel]

Hi


Use
file core

This will tell you what happened.

Please post the output.


Steve Steel

[GRP_2]

We have 3 core files.

- 1st file
The result of "file core" : received SIGBUS
xdb : bus error in the procedure $$dyncall_external

- 2nd file
The result of "file core" : received SIGBUS
xdb : bus error in the procedure $$dyncall_external

- 3rd file
The result of "file core" : received SIGSEGV
xdb : segmentation violation in the procedure _msgd

Thanks in advance ...

[Trond Haugen]

A core file from a binary isn't of much use unless you also have the source and compile it with the '-g' option as steven suggests. That and weeding out the bug from the code is a programmers task.

Regards,
Trond