Skip to content

Compiler crashes found with fuzzing #10121

@rvantonder

Description

@rvantonder

Remember to search before filing a new report

  • I searched for this bug and did not find it in the issue tracker, and furthermore, the title I used above will make this new bug report turn up in the search results for my query.

Zig Version

0.9.0-dev.1583+a7d215759

Steps to Reproduce

Hi, I've been fuzzing the compiler and triaged a bunch of crashes on a recent version that I think you'll find interesting. I'm happy to create an issue for each of these (let me know) but for a start I figure it's easier if to just glance at the findings in this spreadsheet to find ones that might seem more important.

There are 13 unique ones here by my count. I've tried to minimize the programs where possible: https://docs.google.com/spreadsheets/d/1k79eqGpYgXAcwtDbHoIhUjezmlviZrV9M9ueL_JJJ5A/edit#gid=0.

To reproduce, just compile the programs in the second column with zig build-lib <file.zig>

I realize Zig is under heavy development, so don't want this to come across as something that general users are running into, and more as an "FYI these may interest you". These were found as part of a compiler fuzzing project.

Expected Behavior

Compiler probably shouldn't crash for these inputs.

Actual Behavior

Compiler crashes, see spreadsheet. Unfortunately, I don't have a recent development build to give detailed stack traces, but in many cases there isn't any revealing debug info anyway.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugObserved behavior contradicts documented or intended behavior

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions