Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cause of error "Have unordered match in sub-expressions" #406

Open
dchenz opened this issue Jul 4, 2023 · 0 comments
Open

Cause of error "Have unordered match in sub-expressions" #406

dchenz opened this issue Jul 4, 2023 · 0 comments

Comments

@dchenz
Copy link

dchenz commented Jul 4, 2023

Following on from #234, except there are a few things I wasn't sure about and would like to understand the issue in more detail.

The error seems to appear when any pattern in a logical combination ends with $, \b.
E.g.

[
    {
        "id": 100,
        "expr": "hello",
        "flags": "quiet"
    },
    {
        "id": 101,
        "expr": "world$",
        "flags": "quiet"
    },
    {
        "id": 102,
        "expr": "100 & 101",
        "flags": "combination"
    }
]
  • How does having/not having $ affect the matching done by hyperscan, in terms of offsets and reporting inaccurate results? I saw in HS_FLAG_COMBINATION logical error #325 that matching is done at each offset. Is it due it not being able to determine if the current offset is EOL?
  • What does it mean for a pattern to be "unordered"?

Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant