go1.0.1 released

564 views
Skip to first unread message

Andrew Gerrand

unread,
Apr 26, 2012, 6:26:09 PM4/26/12
to golang-nuts
We've just tagged a new Go release: go1.0.1.

This is a minor update to go1. It was issued to fix an escape analysis
bug that can lead to memory corruption. It also includes fixes to
documentation and a few implementation bugs that we thought worth
releasing. Updating to go1.0.1 will require no changes to existing programs.

See the go1 release branch history for the complete list of changes:
      http://code.google.com/p/go/source/list?name=release-branch.go1

Binary distributions are available for the FreeBSD, Linux, Mac OS X,
and Windows operating systems. To install a binary distribution,
follow these instructions:
      http://golang.org/doc/install

If you prefer to build from source, follow these instructions:
      http://golang.org/doc/install/source

Cheers,
Andrew

Peter Kleiweg

unread,
Apr 27, 2012, 5:19:39 AM4/27/12
to golang-nuts
Will there be a release 'weekly' with these changes? I am using some
of the experimental packages, but would also like to have the updates
from go1.0.1.

Jonathan Pittman

unread,
Apr 27, 2012, 7:54:08 AM4/27/12
to Peter Kleiweg, golang-nuts
Not sure if anyone else saw this.  With respect to the new go1.0.1 release, I just ran...

hg pull
hg update release
./all.bash

and then in the middle of the "# Testing packages." section, I saw...


runtime: split stack overflow: 0x2747cd8 < 0x2748000
throw: runtime: split stack overflow

goroutine 1 [chan receive]:
main.(*builder).do(0xf8400fe180, 0xf8401d5000, 0xf8401bb000, 0x1)
/Users/jonathanpittman/go/src/cmd/go/build.go:606 +0x3e4
main.runTest(0x45e598, 0xf840001480, 0x300000003, 0xf8400f6880)
/Users/jonathanpittman/go/src/cmd/go/test.go:367 +0x1aa1
main.main()
/Users/jonathanpittman/go/src/cmd/go/main.go:141 +0x426

goroutine 2 [syscall]:
created by runtime.main
/Users/jonathanpittman/go/src/pkg/runtime/proc.c:221

<some go routines omitted for brevity>

goroutine 342 [syscall]:
syscall.Syscall()
/Users/jonathanpittman/go/src/pkg/syscall/asm_darwin_amd64.s:14 +0x5
syscall.Read(0x6, 0xf840138200, 0x20000000200, 0x0, 0x0, ...)
/Users/jonathanpittman/go/src/pkg/syscall/zsyscall_darwin_amd64.go:810 +0x78
os.(*File).read(0xf8401d4b78, 0xf840138200, 0x20000000200, 0x1c1460, 0x0, ...)
/Users/jonathanpittman/go/src/pkg/os/file_unix.go:163 +0x58
os.(*File).Read(0xf8401d4b78, 0xf840138200, 0x20000000200, 0x0, 0x0, ...)
/Users/jonathanpittman/go/src/pkg/os/file.go:95 +0x83
bytes.(*Buffer).ReadFrom(0xf84080fae0, 0xf840104600, 0xf8401d4b78, 0x0, 0x0, ...)
/Users/jonathanpittman/go/src/pkg/bytes/buffer.go:153 +0x199
io.Copy(0xf84013dba0, 0xf84080fae0, 0xf840104600, 0xf8401d4b78, 0x0, ...)
/Users/jonathanpittman/go/src/pkg/io/io.go:340 +0xc2
os/exec._func_003(0xf84019b050, 0xf8401d4b70, 0x78133, 0x1c1888, 0x445ab, ...)
/Users/jonathanpittman/go/src/pkg/os/exec/exec.go:201 +0x5a
os/exec._func_004(0xf8401d4b50, 0xf840264900, 0x0, 0x0)
/Users/jonathanpittman/go/src/pkg/os/exec/exec.go:260 +0x1e
created by os/exec.(*Cmd).Start
/Users/jonathanpittman/go/src/pkg/os/exec/exec.go:261 +0x65e
go build fmt: exit status 2

and a few lines further down it had...

FAIL fmt [build failed]

I ran all.bash again, but could not reproduce the problem.  Everything built and tested fine.  Thought I would mention it in case it comes up again or is related to some obscure bug.

Peter Kleiweg

unread,
Apr 27, 2012, 8:04:03 AM4/27/12
to golang-nuts
On Apr 27, 1:54 pm, Jonathan Pittman <jonathan.mark.pitt...@gmail.com>
wrote:

>
> FAIL fmt [build failed]
>
> I ran all.bash again, but could not reproduce the problem.  Everything
> built and tested fine.  Thought I would mention it in case it comes up
> again or is related to some obscure bug.

I remember something similar with Go 1. I installed on several
machines. On one machine, I got an error during build. I tried again,
and the error was gone. Don't remember what the error was.

Andrew Gerrand

unread,
Apr 27, 2012, 2:10:45 PM4/27/12
to Peter Kleiweg, golang-nuts
There will be another weekly at some point, but we haven't decided
what the schedule will be.

Andrew

Peter Kleiweg

unread,
Apr 27, 2012, 2:19:45 PM4/27/12
to golang-nuts
On Apr 27, 8:10 pm, Andrew Gerrand <a...@golang.org> wrote:
> On 27 April 2012 21:19, Peter Kleiweg <pklei...@xs4all.nl> wrote:
>
> > Will there be a release 'weekly' with these changes? I am using some
> > of the experimental packages, but would also like to have the updates
> > from go1.0.1.
>
> There will be another weekly at some point, but we haven't decided
> what the schedule will be.

So how do I get a release with both the experimental packages and the
updates from Go 1.0.1? I tried merging 'release' into 'weekly', but
then it refuses to build, saying that the experimental packages are
not allowed to exist.

Kyle Lemons

unread,
Apr 27, 2012, 2:30:16 PM4/27/12
to Peter Kleiweg, golang-nuts
You can build from tip or you can build from go1.0.1, not both.

Uriel

unread,
Apr 28, 2012, 11:35:02 AM4/28/12
to Kyle Lemons, Peter Kleiweg, golang-nuts
Just to be clear: as far as I know the tip has all the fixes from go1.0.1

Still would be nice to have some kind of (approximatedly) time-based snapshots.

minux

unread,
Apr 28, 2012, 11:43:03 AM4/28/12
to Uriel, Kyle Lemons, Peter Kleiweg, golang-nuts
On Sat, Apr 28, 2012 at 11:35 PM, Uriel <ur...@berlinblue.org> wrote:
On Fri, Apr 27, 2012 at 8:30 PM, Kyle Lemons <kev...@google.com> wrote:
> On Fri, Apr 27, 2012 at 11:19 AM, Peter Kleiweg <pkle...@xs4all.nl> wrote:
>
>> So how do I get a release with both the experimental packages and the
>> updates from Go 1.0.1? I tried merging 'release' into 'weekly', but
>> then it refuses to build, saying that the experimental packages are
>> not allowed to exist.
>
> You can build from tip or you can build from go1.0.1, not both.

Just to be clear: as far as I know the tip has all the fixes from go1.0.1
yes. go1.0.1 is made by backport some commits in the default branch to release-branch.go1

Russ Cox

unread,
Apr 30, 2012, 11:21:11 PM4/30/12
to Peter Kleiweg, golang-nuts
On Fri, Apr 27, 2012 at 14:19, Peter Kleiweg <pkle...@xs4all.nl> wrote:
> So how do I get a release with both the experimental packages and the
> updates from Go 1.0.1?

Copy the exp/* tree somewhere else and then use it with Go 1.0.1.

Russ

Russ Cox

unread,
Apr 30, 2012, 11:24:09 PM4/30/12
to Jonathan Pittman, Peter Kleiweg, golang-nuts
On Fri, Apr 27, 2012 at 07:54, Jonathan Pittman
<jonathan.m...@gmail.com> wrote:
> Not sure if anyone else saw this.  With respect to the new go1.0.1 release,
> I just ran...

Thanks. I filed issue 3582.

Russ

josvazg

unread,
May 1, 2012, 5:58:30 AM5/1/12
to golan...@googlegroups.com
In order to install Go 1.0.1 and also get the next updates faster I decided to remove the binary install for Go 1 and get back to pull from the hg repository directly.

Everything worked ok, I removed the go install from /usr/local/go and installed the repo "release" tag on ~/go., but I haven't been able to do all the cleanup.

I don't know where does the Mac binary installer append /usr/local/go/bin to the PATH on my Mac OS X Lion.
(It is not on ~/.profile)
Can you tell me?

Jose

minux

unread,
May 1, 2012, 6:28:03 AM5/1/12
to josvazg, golan...@googlegroups.com
On Tue, May 1, 2012 at 5:58 PM, josvazg <jos...@gmail.com> wrote:
I don't know where does the Mac binary installer append /usr/local/go/bin to the PATH on my Mac OS X Lion.
(It is not on ~/.profile)
Can you tell me?
/etc/paths.d/go
Reply all
Reply to author
Forward
0 new messages