Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/link: panic in (*deadcodepass).flood #33775
Observed on the
Thank you for the report Bryan!
Empirically that code doesn't make sense unless there perhaps was a data race or just data corruption that made s.FuncInfo nil, because the line it is failing on, given commit e764432 as per the logs, the line is
and right before it, we explicitly checked that s.FuncInfo != nil as per
And that code seems to be invoked sequentially.