Bug 2226 - samba 3.0.10 crashes on DGUX on first samba access
samba 3.0.10 crashes on DGUX on first samba access
Status: CLOSED FIXED
Product: Samba 3.0
Classification: Unclassified
Component: Build environment
3.0.9
All other
: P3 normal
: none
Assigned To: Tim Potter
Samba QA Contact
:
Depends on: 2225
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-07 08:38 UTC by Cord Hockemeyer
Modified: 2005-08-24 10:20 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cord Hockemeyer 2005-01-07 08:38:22 UTC
Based on the source code corrections as mentioned in Bug description 2225 I
started the new samba version. As soon as a client tries to connect, I get a
core dump and an abort.

dbx on the core delivers:

bpsy22# dbx ../samba-3.0.10/sbin/smbd core
Type "help" for a list of commands
ELF corefile process information:
  UID   GID   PID  PPID  PGID   SID     SZ COMMAND
    0     0 28055     1 28054  4393    178 /opt/nfs/samba-3.0.10/sbin/smbd -D 
Created on system: dgux bpsy22 R4.20MU04 generic AViiON

Processing object: /opt/nfs/etc/../samba-3.0.10/sbin/smbd
Updating linker symbol table...3986 symbols added. (Total: 3986)
Updating symbolic debugging information...6 modules added. (Total: 6)
Processing object: /usr/dglib/libc.so.1
Updating linker symbol table...1809 symbols added. (Total: 5795)
Updating symbolic debugging information...0 modules added. (Total: 6)
Processing object: /usr/dglib/libresolv.so.1
Updating linker symbol table...41 symbols added. (Total: 5836)
Updating symbolic debugging information...0 modules added. (Total: 6)
Processing object: /usr/dglib/libsocket.so.1
Updating linker symbol table...100 symbols added. (Total: 5936)
Updating symbolic debugging information...0 modules added. (Total: 6)
Processing object: /usr/dglib/libnsl.so.1
Updating linker symbol table...567 symbols added. (Total: 6503)
Updating symbolic debugging information...0 modules added. (Total: 6)
Stopped at pc 0x8003e388 (_kill+12)
*       0x8003e388 _kill+12     jb      __dg_sh_cerror
 core-dump-requested 
 caught signal 6, SIGABRT, abnormal termination, e.g., by abort() -  (core dumped)
(dbx) where
Frame 0, pc 0x8003e388 (_kill+12)
Frame 1, pc 0x816deed (smb_panic2+397)
Frame 2, pc 0x816dd4d (smb_panic+13)
Frame 3, pc 0x815bfa5 (dbgtext+389)
Frame 4, pc 0x815bffb (dbgtext+475)
Frame 5, pc 0x8006a835 (__sigacthandler2+33)
Frame 6, pc 0xffffffff (__libnsl_threads_routines+2146650895)
Frame 7, pc 0x8178a23 (smb_register_charset+435)
Frame 8, pc 0x8178bae (smb_iconv_open+14)
Frame 9, pc 0x815946e (init_iconv+46)
Frame 10, pc 0x80525dd (lp_load+589)
Frame 11, pc 0x81bb67a (reload_services+170)
Frame 12, pc 0x81bbd64 (main+644)
Frame 13, pc 0x804b4a9 (_start+105)

I am sorry but I could not get further information since I have never worked
with dbx before.

Kind regards,
  Cord Hockemeyer
Comment 1 Gerald (Jerry) Carter 2005-02-05 07:57:32 UTC
please retest against 3.0.11 and reopen if necessary.  Also reset 
the version if you reopen the bug report.  Thanks.
Comment 2 Gerald (Jerry) Carter 2005-08-24 10:20:32 UTC
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.