samba - Jul 2005 - smbd (3.0.20pre2) crashes at startup, was: https://bugzilla.samba.org/show_bug.cgi?id=2916

Hi all,
at first glance, samba3.20.pre2 seemed to crash at startup, so I posted 
a bug-report at bugzilla (https://bugzilla.samba.org/show_bug.cgi?id=2916).
After I installed this version in a seperate directory, so it wouldn't 
conflict with any existing *.tdb, but still use the same ldap-directory 
and the same smb.conf, it now starts. I assume that I have some 
.tdb-file or something alike, which is "broken". I am a bit confused 
since all the previous versions worked (currently 3.0.14a). Am I the 
only one who has this problems? Is there a way to identify which file 
causes the problem? I could copy each old .tdb into the new directory 
but are they independent of each other?
System is SuSE9.2 on AMD x86_64, 2.6.8-24.16-default.

with kind regards,
Malte Mueller

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fa. Spezifikum wrote:

| at first glance, samba3.20.pre2 seemed to crash at
| startup, so I posted a bug-report at bugzilla
| (https://bugzilla.samba.org/show_bug.cgi?id=2916).
| After I installed this version in a seperate directory,
| so it wouldn't conflict with any existing *.tdb, but
| still use the same ldap-directory and the same
| smb.conf, it now starts. I assume that I have some
| .tdb-file or something alike, which is "broken". I
| am a bit confused since all the previous versions
| worked (currently 3.0.14a). Am I the only one who
| has this problems? Is there a way to identify which file
| causes the problem? I could copy each old .tdb into the
| new directory but are they independent of each other?
| System is SuSE9.2 on AMD x86_64, 2.6.8-24.16-default.

Malte,

Volker had reproduced that exact backtrace and believed
the bug to be a compiler error.  I'm running SuSE 9.2
on 32-bit systems without a problem.  Are you
sure that the CFLAGS change was applied (based on your
comments in the bug report)?  Could you verify the
CFLAGS in the generated Makefile ?







cheers, jerry
====================================================================Alleviating
the pain of Windows(tm)      ------- http://www.samba.org
GnuPG Key                ----- http://www.plainjoe.org/gpg_public.asc
"I never saved anything for the swim back."     Ethan Hawk in Gattaca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC55IvIR7qMdg1EfYRAnkqAKDCXqFRbfDKaS+g1BUoKXoqH9lXjgCeIcpx
zrZ54z216I5HMqf+nMx++t8=f4BL
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fa. Spezifikum wrote:
> BTW this unexpected behaviour seems still to exist in 
> 3.0.20rc1. It is not a show stopper for me any more. I just
> thought I should mention this.
> 
> With kind regards,
> Malte
> 
> P.S.: I forgot to set CFLAGS to -O this time, sorry. But 
> I assume it wont change anything. If it does I will tell
> on the mailing list.
This has reportedlybeen fixed in the gcc shiped in SLES9 SP2.
Also not that -O is the same thign as -O1 apparently.  So
try again without any optimizations.




cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC9kLrIR7qMdg1EfYRAumJAKCgLaDVHVyNC+AOYgXsSGF3h9P8bwCg7vmY
dPiXfy2notauwSajFAIAe0U=ZjIa
-----END PGP SIGNATURE-----

Shame on me. Why did I think -O was no Optimization? With export 
CFLAGS="-O0" smbd starts. Sorry for wasting your time.

kind regards,
Malte
> 
> This has reportedlybeen fixed in the gcc shiped in SLES9 SP2.
> Also not that -O is the same thign as -O1 apparently.  So
> try again without any optimizations.
> 
> cheers, jerry
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFC9kLrIR7qMdg1EfYRAumJAKCgLaDVHVyNC+AOYgXsSGF3h9P8bwCg7vmY
> dPiXfy2notauwSajFAIAe0U> =ZjIa
> -----END PGP SIGNATURE-----