1. 02 May, 2014 4 commits
    • Alan Donovan's avatar
      runtime: fix bug in GOTRACEBACK=crash causing suppression of core dumps. · 28c515f4
      Alan Donovan authored
      Because gotraceback is called early and often, its cache commits to the value of getenv("GOTRACEBACK") before getenv is even ready.  So now we reset its cache once getenv becomes ready.  Panicking programs now dump core again.
      
      LGTM=rsc
      R=rsc
      CC=golang-codereviews
      https://golang.org/cl/97800045
      28c515f4
    • Dmitriy Vyukov's avatar
      runtime: do not set m->locks around memory allocation · 8afa086c
      Dmitriy Vyukov authored
      If slice append is the only place where a program allocates,
      then it will consume all available memory w/o triggering GC.
      This was demonstrated in the issue.
      Fixes #7922.
      
      LGTM=rsc
      R=golang-codereviews, rsc
      CC=golang-codereviews, iant, khr
      https://golang.org/cl/91010048
      8afa086c
    • Dmitriy Vyukov's avatar
      runtime: make MemStats.LastGC Unix time again · 350a8fcd
      Dmitriy Vyukov authored
      The monotonic clock patch changed all runtime times
      to abstract monotonic time. As the result user-visible
      MemStats.LastGC become monotonic time as well.
      Restore Unix time for LastGC.
      
      This is the simplest way to expose time.now to runtime that I found.
      Another option would be to change time.now to C called
      int64 runtime.unixnanotime() and then express time.now in terms of it.
      But this would require to introduce 2 64-bit divisions into time.now.
      Another option would be to change time.now to C called
      void runtime.unixnanotime1(struct {int64 sec, int32 nsec} *now)
      and then express both time.now and runtime.unixnanotime in terms of it.
      
      Fixes #7852.
      
      LGTM=minux.ma, iant
      R=minux.ma, rsc, iant
      CC=golang-codereviews
      https://golang.org/cl/93720045
      350a8fcd
    • Russ Cox's avatar
      os: cut limited read to 1 GB · 3879f0ab
      Russ Cox authored
      If systems actually read that much, using 2GB-1 will
      result in misaligned subsequent reads. Use 1GB instead,
      which will certainly keep reads aligned and which is
      plenty large enough.
      
      Update #7812.
      
      LGTM=bradfitz
      R=bradfitz
      CC=golang-codereviews
      https://golang.org/cl/94070044
      3879f0ab
  2. 01 May, 2014 4 commits
  3. 30 Apr, 2014 5 commits
  4. 29 Apr, 2014 6 commits
  5. 28 Apr, 2014 9 commits
  6. 27 Apr, 2014 8 commits
  7. 26 Apr, 2014 4 commits