16.12.2024 01:49, Mrten wrote:
On 14/12/2024 04:13, Andrew Bartlett wrote:
If Samba has no interfaces to bind to, it will panic, which triggers a
backtrace, but this is intentional and controlled, not a segmentation fault.
OK, thank you for that. I think these systemd messages threw me off:
Dec 14 00:59:01 kyra systemd[1]: smbd.service: Main process exited,
code=dumped, status=6/ABRT
Dec 14 00:59:01 kyra systemd[1]: smbd.service: Failed with result 'core-dump'.
Then the subject of the mail I got: "Panic or segfault in Samba" which is
technically true but I have no way to differentiate between the two...
I'd say this is a wishlist bug report now, wishing to handle such
situation in a more user-friendly way on the samba side.
If wouldn't know what to do with this issue either, if Andrew didn't
step in.
Anyway, it's expected. Still, samba-dbgsym does not exist.
It does. See https://wiki.debian.org/HowToGetABacktrace
https://packages.debian.org/search?keywords=samba-dbgsym&searchon=names&suite=stable§ion=all
I saw it does exist in sid...
/mjt
