On Wed, Apr 7, 2021 at 1:47 PM sro...@gmail.com <sros...@gmail.com> wrote: > > Is there a way to analyze a go program and determine whether it is > susceptible to bug https://github.com/golang/go/issues/45175? > While the obvious solution is to upgrade to 1.15.11 or 1.16.3, it would still > be useful to analyze existing programs, either as a compiled binary or source > code.
There is no simple way to do this. It's an unfortunate bug, but it's rare, and is dependent on the exact compilation process. The simplest way to detect a possible problem might be to compile the package with both 1.15.10 and 1.15.11 and compare the generated output. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcX2n%2BeGy8RG9-9jG%2BeOo8%2B8hRqT1R2Qg9TVM01iwOqzhQ%40mail.gmail.com.
