Xiang Wang
Xiang Wang
Yes, you have to use callback function. Any specific reason why you want to avoid callback?
Already answered at https://github.com/intel/hyperscan/issues/189.
Yes, the results are not guaranteed if you modified your input string at the middle of matching.
Any reason to increase the size? The performance impact depends on your specific use case, and we don't recommend to change the size manually.
No, but I don't think there could be large efforts using these APIs in C++. Hyperscan compile time is written with C++ to make our analysis easier, but run-time is...
Hi @onexpiece, We only support C/C++ and don't provide official go binding. It'll be good if you can run your test case with our native C code to see whether...
Hi all, Once we have more rules to add, all the rules need to be compiled to a new database again. To get the best performance, the compilation of Hyperscan...
I can't reproduce your error. Can you find the exact place in the building script that triggers this `invalid option` error?
Hi @rejohn, Which version of Hyperscan did you use? It'll be good if you can show us your full CMake compile command and the GDB trace.
Thanks. This is due to a change in our release 5.2 which replaced `hs_compile_multi()` with `hs_compile_multi_int()` at https://github.com/intel/hyperscan/blob/4cebdaa435f1f52e96450e066937b3835b9b7047/tools/hsbench/engine_hyperscan.cpp#L431 We'll fix it shortly in our bugfix release.