swat version 3.0.22-1ubuntu1 crashes on start (dapper)

[Sirius Rayner-Karlsson]

I installed swat to admin my smb.conf, used to work fine on breezy. On latest dapper - no cigar.

I have so far tried running it through gdb and with strace. The gdb output is:

# gdb /usr/sbin/swat
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/sbin/swat
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1213155104 (LWP 20176)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1213155104 (LWP 20176)]
0x080fa965 in toupper_w ()
(gdb) thread show all bt
No symbol table is loaded. Use the "file" command.
(gdb) bt
#0 0x080fa965 in toupper_w ()
#1 0x080fb9e4 in toupper_ascii ()
#2 0x080f7c1c in strupper_m ()
#3 0x080fcc5f in set_global_myname ()
#4 0x0807cedf in lp_load ()
#5 0x08074002 in status_page ()
#6 0x0807598e in main ()
(gdb)

strace is more verbose, and I'll attach the output as a file instead.

[Sirius Rayner-Karlsson (trudheim)]

Just the strace output.

[Sirius Rayner-Karlsson (trudheim)]

Snippet from /var/log/samba/log.swat:

[2006/04/17 21:39:48, 0] lib/fault.c:fault_report(40)
  ===============================================================
[2006/04/17 21:39:48, 0] lib/util.c:smb_panic2(1554)
  PANIC: internal error
[2006/04/17 21:39:48, 0] lib/util.c:smb_panic2(1562)
  BACKTRACE: 12 stack frames:
   #0 swat(smb_panic2+0x78) [0x80feb88]
   #1 swat(smb_panic+0x19) [0x80fed85]
   #2 swat [0x80eceb5]
   #3 [0xffffe420]
   #4 swat(toupper_ascii+0x12) [0x80fb9e4]
   #5 swat(strupper_m+0x1e) [0x80f7c1c]
   #6 swat(set_global_myname+0x3f) [0x80fcc5f]
   #7 swat(lp_load+0x202) [0x807cedf]
   #8 swat [0x8074002]
   #9 swat(main+0x117) [0x807598e]
   #10 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7c40ea2]
   #11 swat [0x8070e21]

HTH,

[Sitsofe Wheeler (sitsofe)]

It might be interesting to know what your machine name is within the /etc/samba/smb.conf file - could you attach it using malone's Add Attachment link at the left?

[Sirius Rayner-Karlsson (trudheim)]

Hi,

Thanks for looking at the defect. The smb.conf contains nothing unusual, and all I wanted swat for was to twiddle a few things while tinkering with printing from a winxp box. As it stands, I have printing warking and I did not have to touch smb.conf at all, but swat still crashes. Also, the smb.conf I have was generated with swat, but on Breezy.

Regards,

[raxius (raxius)]

i have the same problem. I tested it on the i386 and the amd64 version of the ubuntu server installation. I have dapper beta.

i386 - log.swat

[2006/04/24 21:45:18, 0] lib/util.c:smb_panic2(1554)
  PANIC: internal error
[2006/04/24 21:45:18, 0] lib/util.c:smb_panic2(1562)
  BACKTRACE: 12 stack frames:
   #0 swat(smb_panic2+0x78) [0x80feb88]
   #1 swat(smb_panic+0x19) [0x80fed85]
   #2 swat [0x80eceb5]
   #3 [0xffffe420]
   #4 swat(toupper_ascii+0x12) [0x80fb9e4]
   #5 swat(strupper_m+0x1e) [0x80f7c1c]
   #6 swat(set_global_myname+0x3f) [0x80fcc5f]
   #7 swat(lp_load+0x202) [0x807cedf]
   #8 swat [0x8074002]
   #9 swat(main+0x117) [0x807598e]
   #10 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7c21ea2]
   #11 swat [0x8070e21]

amd64 - log.swat

[2006/04/24 21:17:05, 0] lib/util.c:smb_panic2(1554)
  PANIC: internal error
[2006/04/24 21:17:05, 0] lib/util.c:smb_panic2(1562)
  BACKTRACE: 11 stack frames:
   #0 swat(smb_panic2+0x66) [0x4c3986]
   #1 swat [0x4b0e57]
   #2 /lib/libpthread.so.0 [0x2aaaaae7f4d0]
   #3 swat(toupper_w+0x1d) [0x4bf48d]
   #4 swat(toupper_ascii+0x8) [0x4c0898]
   #5 swat(strupper_m+0x1c) [0x4bc40c]
   #6 swat(set_global_myname+0x3e) [0x4c1b4e]
   #7 swat(lp_load+0x20f) [0x43e32f]
   #8 swat(main+0xd9) [0x436489]
   #9 /lib/libc.so.6(__libc_start_main+0xdb) [0x2aaaabe2f49b]
   #10 swat [0x43180a]

[Nicolas Gama (gama-nicolas)]

It seems to be the same problem as bug# 39990 and 39484:
the segmentation fault is due to an uninitialized table "upcase_table"

For my computer, the patch given in bug 39990 fixes it: see
https://launchpad.net/distros/ubuntu/+source/samba/+bug/39990

[Adam Conrad (adconrad)]

Fixed in 3.0.22-1ubuntu2.