fix unreachable code after log.Fatal in fuzzing corpus generator

[Abirdcfly]

https://pkg.go.dev/log#Fatal

Fatal is equivalent to Print() followed by a call to os.Exit(1).

see https://go.dev/play/p/fWIT3Iobb0A for example:

package main

import (
	"fmt"
	"log"
)

func main() {
	log.Fatalf("print and exit")
	fmt.Println("will not execute")
}

/* output
2009/11/10 23:00:00 print and exit

Program exited.
*/

[codecov]

Codecov Report

Merging #3496 (bea5de0) into master (bea5de0) will not change coverage.
The diff coverage is n/a.

❗ Current head bea5de0 differs from pull request most recent head ddddf4a. Consider uploading reports for the commit ddddf4a to get more accurate results

@@           Coverage Diff           @@
##           master    #3496   +/-   ##
=======================================
  Coverage   85.69%   85.69%           
=======================================
  Files         136      136           
  Lines        9992     9992           
=======================================
  Hits         8562     8562           
  Misses       1052     1052           
  Partials      378      378           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[marten-seemann]

@Abirdcfly Can you please rebase this PR on top of the current master? The lint job is failing consistently, and I'm not sure if that's due to changes in the CI setup or if it's something related to this PR.

[marten-seemann]

Can you rebase please, not merge master?

[marten-seemann]

It worked, great! Thank you!