eDir core when stopping DCS driver


Had something odd happen today, I was import a LDIF file containing
about 1 million users, it was at about 780 000 when I decided I wanted
to stop the DCS driver because the Reporting database was having some

When I clicked Stop, eDirectory stopped responding.

No core file was created even though the hs_err_pid file tells me it
should be here:
/var/opt/novell/eDirectory/data/dib/core or core.2145

This is SLES12SP3 with IDM 4.7.1.

ulimit reports unlimited

I would really like a core file next time, what can I do?

This is from the hs_err_pid file:

# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00007fc68c3ff2b8, pid=2145, tid=0x00007fc633683700
# JRE version: Java(TM) SE Runtime Environment (8.0_172-b11) (build
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.172-b11 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# C [libzoomdb.so 0x292b8] FlmRecordRetrieve(void*, unsigned long,
unsigned long, unsigned long, FlmRecord**, unsigned long*) 0x78
# Core dump written. Default location:
/var/opt/novell/eDirectory/data/dib/core or core.2145
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

--------------- T H R E A D ---------------

Current thread (0x000000001281d000): JavaThread "DCS-CacheReader"
[_thread_in_native, id=3938, stack(0x00007fc633583000,0x00007fc633684000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 128 (SI_KERNEL), si_addr:


If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.