nmbd crashed with SIGSEGV in _IO_vfprintf_internal()

[steubens]

Binary package hint: samba

I was greeted with the crash message in the morning; first time I've ever seen it, no context

ProblemType: Crash
Architecture: amd64
Date: Sat Jan 30 13:56:29 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/nmbd
Package: samba 2:3.4.0-3ubuntu5.4
ProcCmdline: /usr/sbin/nmbd -D
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: samba
StacktraceTop:
 ?? ()
 _IO_vfprintf_internal (s=0x7fffa8304440,
 ___vsnprintf_chk (s=0x7fffa83045df "",
 talloc_vasprintf () from /usr/lib/libtalloc.so.1
 talloc_asprintf () from /usr/lib/libtalloc.so.1
Title: nmbd crashed with SIGSEGV in _IO_vfprintf_internal()
Uname: Linux 2.6.31-18-generic x86_64
UserGroups:

[Chuck Short (zulcss)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

[steubens (steubens)]

i have no clue as to reproducing it; it happened once and hasn't since that time, i reported it in case the apport report might be useful/obvious

[Chuck Short (zulcss)]

User is no longer able to reproduce.

chuck

[Hans Deragon (deragon)]

I had the same problem again in 2018, under Ubuntu 18.04. The automatic reporting tool for Ubuntu showed me this bug report, to which I subscribed. How should I reopen this bug report?

[Andreas Hasenack (ahasenack)]

I suggest you open a new bug with your crash info. This one is too old.