Am Wed, 26 Nov 2014 19:41:39 +1000 schrieb Da Rock openldap-technical@herveybayaustralia.com.au:
On 26/11/2014 18:23, Ulrich Windl wrote:
What you could try is (assuming you have debug symbols in your binary) attaching gdb to the running slapd to see where it is spending CPU time. I can't remember the commands precisely, but "bt (backtrace)" and "info threads" should point you in the right direction. Note that slapd will likely stop responding while gdb is attached, so you could also try to force a core dump for offline examination.
I'm not sure I follow here. How would this work? I attach gdb to the running slapd I get, but if it stops how does that help me? I've only had a little bit of experience with gdb...
How would I get a core dump, as well? That sounds like it might be more useful.
[...] ulimit -c unlimited
-Dieter