commit da9759ca307d8a24c0bedce3a771d3cb79b96cbd
author Alan Donovan <adonovan@google.com> Thu Jun 22 09:35:10 2017 -0400
committer Alan Donovan <adonovan@google.com> Fri Jun 23 02:24:18 2017 +0000
tree 8719a5f51538736eb232fe6c780f2e6ba1859f76
parent 1ab5277e8379405f090b5901d5b1ce812e172969

cmd/bundle: fix nil dereference panic

In the loader API, (*Config).Import, like go/build, accepts relative
paths such as ".", but (*Program).Package requires the exact path of a
loaded package.  So, to find the package identified by "." we must
look at the set of packages actually loaded, which in this scenario is
guaranteed to be a singleton.

(This is a definite weakness of the loader API.  In the more general
case where two or more packages are imported, it's tricky to correlate
the calls to Import with the package(s) each call actually loads.)

Fixes golang/go#20751

Change-Id: I925e969c9b4f4d6b6344c16f156b47857436d70a
Reviewed-on: https://go-review.googlesource.com/46414
Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>