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

--dfs-exhaustive/--max-exhaustive-depth do not appear to work #152

Open
dgopstein opened this issue Aug 8, 2023 · 1 comment
Open

--dfs-exhaustive/--max-exhaustive-depth do not appear to work #152

dgopstein opened this issue Aug 8, 2023 · 1 comment
Labels

Comments

@dgopstein
Copy link

dgopstein commented Aug 8, 2023

I tried running --dfs-exhaustive in the following ways, and got the following errors:

$ csmith --dfs-exhaustive
error: options conflict - max-exhaustive-depth must be at least 0

$ csmith --dfs-exhaustive --max-exhaustive-depth
expect arg at pos 3

$ csmith --dfs-exhaustive --max-exhaustive-depth 0
error: options conflict - max-exhaustive-depth must be at least 0

$ csmith --dfs-exhaustive --max-exhaustive-depth 1
Assertion failed: ("request random number in an error state. " && 0), function random_choice, file .../csmith/src/DFSRndNumGenerator.cpp, line 286.
[1]    25559 abort      csmith --dfs-exhaustive --max-exhaustive-depth 1

$ csmith --dfs-exhaustive --max-exhaustive-depth 2
<exit status 0, no output>

$ csmith --dfs-exhaustive --max-exhaustive-depth 3
[1]    25629 segmentation fault  csmith --dfs-exhaustive --max-exhaustive-depth 3

$ csmith --dfs-exhaustive --max-exhaustive-depth 4
[1]    25664 segmentation fault  csmith --dfs-exhaustive --max-exhaustive-depth 4

$ csmith --dfs-exhaustive --max-exhaustive-depth 20
[1]    25699 segmentation fault  csmith --dfs-exhaustive --max-exhaustive-depth 20

Is there some other way to run --dfs-exhaustive that I haven't tried?

Thanks!

@eeide
Copy link
Member

eeide commented Aug 8, 2023

Thank you for your bug report!

I don't have any advice or solution to offer you. It looks like --dfs-exhaustive is broken/bitrotted, and will need to be debugged before anyone can use it.

@eeide eeide added the Bug label Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants