#49349 Python Exception global name 'imap' is not defined:
Closed: wontfix Opened by vashirov.

Issue Description

When I generate stacktrace using gdb, it does't print the thread contents:

Core was generated by `/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-deftestinst -i /var/run/dirsrv/slapd-de'.
Program terminated with signal 11, Segmentation fault.
#0  __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at ../nptl/pthread_mutex_lock.c:66
66        unsigned int type = PTHREAD_MUTEX_TYPE_ELISION (mutex);
Python Exception <type 'exceptions.NameError'> global name 'imap' is not defined: 
Python Exception <type 'exceptions.NameError'> global name 'imap' is not defined: 
Thread 2 (Thread 0x7faa31bd18c0 (LWP 31874)):
Thread 1 (Thread 0x7faa164ff700 (LWP 31899)):

Package Version and Platform

389-ds-base-1.3.7.1-20170814git63ea19dcb.el7.x86_64
Python 2.7.5

Steps to reproduce

gdb -ex 'set confirm off' -ex 'set pagination off' -ex 'thread apply all bt full' -ex 'quit' /usr/sbin/ns-slapd /var/log/dirsrv/slapd-INSTANCENAME/core.PID > stacktrace.`date +%s`.txt 2>&1


Metadata Update from @vashirov:
- Issue assigned to vashirov

Metadata Update from @vashirov:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to review
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to ack (was: review)

To ssh://pagure.io/389-ds-base.git
63ea19dcb..f114f699b master -> master

Metadata Update from @vashirov:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2408

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata