net ads join: memory fault

[enrico.nic]

Hi,

I am experiencing a "core dump" message after trying to join a Windows 2003 domain, on an HP-UX samba server (HP CIFS Server A.02.03.04a) on HP-UX 11v1.
The strange thing is that on a DEV server, with identical operating system (the only difference is that the DEV system is 32 bit, the PROD system is 64 bit), all seems to function correctly.
On both systems I have installed the latest CIFS server, Kerberos client, LDAP-UX integration and PAM Kerberos software - and on the two systems the sw releases are identical.
The configuration files for Kerberos (krb5.conf) and the CIFS server (smb.conf) are identical, at least in the [global] section for smb.conf.
This is the output (the last lines) from a
# net ads join -U myusername -d 10
[2008/09/24 21:15:01, 4] libads/ldap.c:ads_server_info(2608)
time offset is 0 seconds
[2008/09/24 21:15:01, 5] lib/smbldap.c:smb_ldap_start_tls(535)
smb_ldap_start_tls: not ldap ssl start tls
[2008/09/24 21:15:01, 4] libads/sasl.c:ads_sasl_bind(455)
Found SASL mechanism GSS-SPNEGO
Bus error(coredump)

Any help would be appreciated.

Thank you

Enrico

[Dennis Handly]

What does "file core" show?
You could download gdb and get a stacktrace to see if anything is useful.

[enrico.nic]

Hi,

A "file core" command gives the following output:
core: core file from 'net' - received SIGSEGV

I tried to reinstall the Kerberos client (rel. C 1.3.5.06) without luck.

I don't know how to use 'gdb' ...

Any other help would be appreciated.

Thank you

[Dennis Handly]

>I don't know how to use 'gdb'

(This won't solve the problem but it may help others triage it by matching some known issue.)

To use gdb:
gdb net core
(gdb) bt
(gdb) info reg
(gdb) disas $pc-4*20 $pc+4*4
(gdb) q

You should attach a text file with this output.

You can make gdb output directly to a file by:
(gdb) set redirect-file gdb.out
(gdb) set redirect on
Then do the above bt ... commands
If you want to turn redirection off:
(gdb) set redirect off

[enrico.nic]

Hi,

I have redirected the 'gdb' output as of your instructions: in the attached file the result.

Enrico

[Dennis Handly]

>I have redirected the 'gdb' output

Sorry, I must have missed this until now.

Basically you are in ber_free_buf at io.c:176.
A field 32 bytes into a struct pointed to by the first argument has a bad pointer and it aborts when using that pointer.