You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using lizard in a tool I manage called Statick. When we run lizard we use the -w flag by default, and we are seeing lizard crash. I am seeing the same behavior when running the lizard tool on its own. This behavior does not happen in v1.17.10, but it does occur in 1.17.17. I have narrowed it down to a change between v1.17.14 and v1.17.15, persisting on through v1.17.17.
A minimal example is to use the C file at the bottom of this post as input. Save it as test.c. Then run
lizard test.c
That runs fine. Now add the -w flag. This crashes with Traceback
$ lizard --version
1.17.17
$ lizard -w test.c
Traceback (most recent call last):
File "/home/thomas/.local/bin/lizard", line 8, in<module>sys.exit(main())
File "/home/thomas/.local/lib/python3.10/site-packages/lizard.py", line 1079, in main
warning_count = printer(result, options, schema, AllResult)
File "/home/thomas/.local/lib/python3.10/site-packages/lizard.py", line 855, in print_clang_style_warning
print(scheme.clang_warning_format().format(f=warning))
AttributeError: 'FunctionInfo' object has no attribute 'max_nesting_depth'
In v1.17.14 there is no problem and I see the warning.
I am using lizard in a tool I manage called Statick. When we run lizard we use the
-w
flag by default, and we are seeing lizard crash. I am seeing the same behavior when running the lizard tool on its own. This behavior does not happen in v1.17.10, but it does occur in 1.17.17. I have narrowed it down to a change between v1.17.14 and v1.17.15, persisting on through v1.17.17.A minimal example is to use the C file at the bottom of this post as input. Save it as
test.c
. Then runThat runs fine. Now add the
-w
flag. This crashes with TracebackIn v1.17.14 there is no problem and I see the warning.
The test.c file I am using is
The text was updated successfully, but these errors were encountered: