nodirt/ggt: src/log.go; 3 LoC

Found a possible issue in [nodirt/ggt](https://www.github.com/nodirt/ggt) at [src/log.go](https://github.com/nodirt/ggt/blob/20e557ef54d9f491a5a9428183a07cc32c185f11/src/log.go#L164-L166)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

>

[Click here to see the code in its original context.](https://github.com/nodirt/ggt/blob/20e557ef54d9f491a5a9428183a07cc32c185f11/src/log.go#L164-L166)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, b := range bs {
printBenchmark(&b)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {printBenchmark 1} was not found in the callgraph; reference was passed directly to third-party code
```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 20e557ef54d9f491a5a9428183a07cc32c185f11

Read src/log.go at lines 164-166 and the linked Go context, then review how printBenchmark is used. Decide whether the analyzer finding is a Bug, Mitigated, or Desirable Behavior and leave the corresponding reaction; completion is the classification reaction.

Written by the indexing model from the issue text.