[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: (ITS#9023) crash using ppolicy chaining from slave to master
- To: openldap-its@OpenLDAP.org
- Subject: RE: (ITS#9023) crash using ppolicy chaining from slave to master
- From: quanah@symas.com
- Date: Fri, 17 May 2019 15:30:54 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
--On Friday, May 17, 2019 4:09 PM +0000 "AYANIDES, JEAN-PHILIPPE"
<jpayanides@prosodie.com> wrote:
>
>
> Hello Quanah,
>
> I am not very familiar with gdb. Can you help me doing that?
Start slapd on the server that's crashing
Get the process ID of slapd
gdb /path/to/slapd PID
For example, if slapd is located in /usr/sbin, and the process ID is 1234:
gdb /usr/sbin/slapd 1234
At the (gdb) prompt, enter the command "cont" to continue execution
Run your operation that causes slapd to crash. This should drop you back
to the (gdb) prompt.
Then run the command:
thr apply all bt full
This will provide the full backtrace.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>