Re: Perl debugger fixes bug, now i've got a perl debugger to get rid of.

Another thought is to reduce the debug level you specify in your bind() parameters. You may be timing out the connection while the server side is generating a few metric tons of 'debugging' data. FWIW, I tried the LDAP debug levels exactly once, because I wanted to see what it gave me. 'debug=>1' generated over 1000 lines of response, and that was for a successful bind(}! I don't want to know how much I get back for level 15.

----
I Go Back to Sleep, Now.

OGB

Comment on Re: Perl debugger fixes bug, now i've got a perl debugger to get rid of.

Replies are listed 'Best First'.
Re: Re: Perl debugger fixes bug, now i've got a perl debugger to get rid of. by emeitner (Novice) on Feb 22, 2004 at 21:52 UTC
I have already run it with the debugging turned off. There was no change in the behavior. The same script on another machine works with it set to maximum. Calling sync() before bind() and search() produces: Can't use an undefined value as a HASH reference at /usr/share/perl5/Net/LDAP.pm line 696, <DATA> line 225. The docs say that sync() should accept null arguments....	[reply]
Re: Re: Re: Perl debugger fixes bug, now i've got a perl debugger to get rid of. by Corion (Patriarch) on Feb 22, 2004 at 22:05 UTC
Could you produce and post a small sample program that exhibits this behaviour? From looking at the source, I believe that `$ldap->{net_ldap_mesg}` does not exist/is not filled/is undef. Whether this makes sense when you call `$ldap->sync()`, I don't know, but it would help in debugging the error. Maybe you need to call some other method before you can call `sync()`? For example if you have no outstanding messages?	[reply]