rspamd binaries fail with illegal instruction 4:

Steven Smith steve.t.smith at
Fri Sep 13 11:16:49 UTC 2019

I’m not an expert either, but it looks like it’s related to hyperscan (“ue2::hs_compile_multi_int”).

Possibly related:

I suggest two paths:

1. Poke at hyperscan and see if that’s the problem on this specific architecture.

2. That’s exactly the information the upstream author needs to pinpoint the problem. Please open an issue at and post that very same lldb output, along with the error message, and ask for help there. He’ll probably send you along to hyperscan, but would also have insight if it’s something rspamd-specific.

> I was finally able to run a test on the failing rspamd, I am not familiar with reading this core dumps and followed the instructions given in the URL, i got following from lldb:
> lldb `which /opt/local/bin/rspamd` -c /cores/core.89034 
> (lldb) target create "/opt/local/bin/rspamd" --core "/cores/core.89034"
> Core file '/cores/core.89034' (x86_64) was loaded.
> (lldb) bt all
> * thread #1, stop reason = signal SIGSTOP
>   * frame #0: 0x000000000f4c74b1 librspamd-server.dylib`ue2::hs_compile_multi_int(char const* const*, unsigned int const*, unsigned int const*, hs_expr_ext const* const*, unsigned int, unsigned int, hs_platform_info const*, hs_database**, hs_compile_error**, ue2::Grey const&) + 513
>     frame #1: 0x000000000f4c7c40 librspamd-server.dylib`hs_compile_multi + 96
>     frame #2: 0x000000000f2daff5 librspamd-server.dylib`rspamd_multipattern_compile + 370
>     frame #3: 0x000000000f376b70 librspamd-server.dylib`rspamd_language_detector_init + 5664
>     frame #4: 0x000000000f31d570 librspamd-server.dylib`rspamd_config_read + 1262
>     frame #5: 0x000000010d479de8 rspamd`load_rspamd_config + 107
>     frame #6: 0x000000010d479499 rspamd`main + 1373
>     frame #7: 0x00007fff55d0f015 libdyld.dylib`start + 1
> (lldb) 
> It created two core dumps every minute until I unloaded rspamd.
> Regards,
> Horst
>>> On 10 Sep 2019, at 11:40, Steven Smith <steve.t.smith at> wrote:
>>> AVX was just a guess. Based in the above it could be sse 4.2 that is the issue. The machine that is failing lacks this (which actually makes that cpu pretty old I would guess)
>> A core dump is the most efficient diagnostic. It’s fast and easy. The modern macOS instructions are here:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-users mailing list