Alfred Klomp

Re: fixed, if that's the cause, it would still be a very serious bug. You could check if that's really the cause by opening a shell, unsetting HOME, and running...

A missing `$HOME` seems like such a weird cause for a segfault, since I can't think of a good reason why libsmbclient has to know it. Its smb.conf is usually...

Found [some documentation](https://www.szabilinux.hu/php/zend.variables.resource.html) that claims that resource list pointers don't need to be threadsafe. Makes sense. So my test branch fixes what isn't broken.

Thanks. You may want to anonymize that. So it's a `strlen` somewhere when allocating a new context. Interesting!

So as I read the stack trace, we first call `smbclient_state_new`, then that calls `smbc_new_context` inside libsmbclient, and then after some jumping around, we get a segfault when executing `strlen`....

The warning about the resource being a boolean occurs because `smbclient_state_new()` is returning `false` for some reason. Feeding `false` to `smbclient_state_init()` will make it complain about an unexpected parameter type....

Then we're in the twilight zone. As I see it, _either_ `smbclient_state_new()` returns `false` and prints an error, _or_ it allocates an internal data structure and returns a resource. It...

Found [this bug](https://bugzilla.samba.org/show_bug.cgi?id=9038) in Samba's Bugzilla about exactly this issue.

The `objcopy` step is not really necessary and can be commented out. It hides any symbols not listed in `lib/exports.build.txt`, so that internal symbols are not exposed by accident. The...