That's a great idea. Thank you! I am doing that right now.
On Wed, Apr 7, 2021 at 5:05 PM 'Keith Randall' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> If you look at CL 304251, there's one place where we added "return false".
> Put a panic just before that line (in 1.15.11 or
If you look at CL 304251, there's one place where we added "return false".
Put a panic just before that line (in 1.15.11 or 1.16.3), rebuild the
compiler, then rebuild your program and see if your program triggers that
panic.
On Wednesday, April 7, 2021 at 2:37:53 PM UTC-7 Ian Lance Taylor
On Wed, Apr 7, 2021 at 1:47 PM sro...@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
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.
