On Tue, 2022-05-24 at 14:25 +0300, Michael Tokarev
wrote:> 17.05.2022 06:54, Andrew Bartlett via samba wrote:
> > Honestly, what we need is the backtrace. For some reason these
pakages
> > have been built without our backtrace support, so please find and use
> > the gdb_backtrace script as a panic action, eg
>
> Hi Andrew!
>
> What do you mean "built without backtrace support"? How one
builds with
> or without backtrace support, - I don't know this term.
>
> If you're referring to gcc -g when compiling (debugging info), that is
> shipped in separate packages in Debian, samba-dbgsym (and samba-libs-dbgsym
> etc), https://wiki.debian.org/HowToGetABacktrace describes how to install
> these -dbgsym packages.
This is sort of the inverse of what this MR is about:
https://gitlab.com/samba-team/samba/-/merge_requests/2534
In short, if libunwind is found on the system at build time, Samba will
do an internal stack unwind that at least gives us a first clue, but
ideally we need the full gdb backtrace, ideally by having the
gdb_backtrace script packaged so the admin can specify it.
Long ago Debian packages used to mail the admin when Samba crashed with
a backtrace, I don't know when that stopped happening.
"We" should add info on installing the right packages and enabling
this
to https://wiki.samba.org/index.php/Bug_Reporting to give folks a clue
so I stop repeating myself on the lists...
Andrew Bartlett
--
Andrew Bartlett (he/him) https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Developer, Catalyst IT https://catalyst.net.nz/services/samba