EAccessViolation

[lighth7015]

While exiting LdapAdmin, I receive the following error(s)

WARNING: TQtThemeServices.DrawEdge is not implemented.
WARNING: TQtThemeServices.DrawEdge is not implemented.
WARNING: TQtThemeServices.DrawEdge is not implemented.
Heap dump by heaptrc unit
0 memory blocks allocated : 0/0
0 memory blocks freed     : 0/0
0 unfreed memory blocks : 0
True heap size : 0
True free heap : 0
An unhandled exception occurred at $00007F3056306BFC:
EAccessViolation: 
  $00007F3056306BFC

An unhandled exception occurred at $00007F30562DD3CC:
EAccessViolation: 
  $00007F30562DD3CC

An unhandled exception occurred at $00007F3056306BFC:
EAccessViolation: 
  $00007F3056306BFC

kf5.kio.core.dirlister: 
An unhandled exception occurred at $00007F305623D573:
EAccessViolation: 
  $00007F305623D573
  $0000000002DE6568

An unhandled exception occurred at $00007F3056306BFC:
EAccessViolation: 
  $00007F3056306BFC

[ibv]

Hi,
what linux distribution was used?
You are using KDE, Gnome or others desktop environment?
LDAP-Admin is compiled by default with the gtk2 libraries.

[lighth7015]

KDE, and my distro is ArchLinux.

[ibv]

Can you please run this command strace ./LdapAdmin
and exploring the result ?
I tried LdapAdmin in Arch Linux 2019.05 (VirtualBox, https://www.osboxes.org/arch-linux/)
and the program worked without the specified error.

[lighth7015]

Definitely! And on the console?

[ibv]

Here is a partial listing of the results from Mageia 7,

at the end of the report, the data is stored in the reg.xml file

and the memory is freed.
Is the ~/.config/LdapAdmin/reg.xml created after running LdapAdmin?

[lighth7015]

Apologies, I got tied up with work. But it appears to be hanging waiting for a futex

futex(0x10dc5d0, FUTEX_WAIT_PRIVATE, 0, NULL

And yes, the file exists.

[ibv]

You are using your own LdapAdmin compilation or downloaded from the release section?

[lighth7015]

I cloned this repository.

[ibv]

Hi,
I really have no idea where the problem may be,
a similar bug was fixed in commit b57fab8,
possible solution how to detect a bug is to step the exit of the program in the debugger.

[fxrsliberty]

I really wish this worked... it's a great tool on Windows but I live on linux all the time and only use windows to administer the AD