An error occurred fetching the project authors.
  1. 15 Mar, 2018 1 commit
  2. 14 Mar, 2018 1 commit
  3. 13 Feb, 2018 2 commits
  4. 08 Jun, 2017 2 commits
  5. 09 Jun, 2016 1 commit
  6. 10 Apr, 2015 1 commit
  7. 30 Mar, 2015 1 commit
    • Lee Packham's avatar
      runtime: allow pointers to strings to be printed · c45751e8
      Lee Packham authored
      Being able to printer pointers to strings means one will able to output
      the result of things like the flag library and other components that use
      string pointers.
      
      While here, adjusted the tests for gdb to test original string pretty
      printing as well as pointers to them. It was doing it via the map before
      but for completeness this ensures it's tested as a unit.
      
      Change-Id: I4926547ae4fa6c85ef74301e7d96d49ba4a7b0c6
      Reviewed-on: https://go-review.googlesource.com/8217
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarIan Lance Taylor <iant@golang.org>
      c45751e8
  8. 25 Feb, 2015 1 commit
  9. 22 Feb, 2015 1 commit
    • Jan Kratochvil's avatar
      gdb: fix "gdb.error: No struct named reflect.rtype." · 02d80b9e
      Jan Kratochvil authored
      With a trivial Golang-built program loaded in gdb-7.8.90.20150214-7.fc23.x86_64
      I get this error:
      
      (gdb) source ./src/runtime/runtime-gdb.py
      Loading Go Runtime support.
      Traceback (most recent call last):
        File "./src/runtime/runtime-gdb.py", line 230, in <module>
          _rctp_type = gdb.lookup_type("struct reflect.rtype").pointer()
      gdb.error: No struct type named reflect.rtype.
      (gdb) q
      
      No matter if this struct should or should not be in every Golang-built binary
      this change should fix that with no disadvantages.
      
      Change-Id: I0c490d3c9bbe93c65a2183b41bfbdc0c0f405bd1
      Reviewed-on: https://go-review.googlesource.com/5521Reviewed-by: default avatarIan Lance Taylor <iant@golang.org>
      02d80b9e
  10. 17 Feb, 2015 2 commits
  11. 15 Jan, 2015 1 commit
  12. 08 Sep, 2014 1 commit
  13. 20 May, 2014 1 commit
  14. 24 Feb, 2014 1 commit
  15. 10 Sep, 2013 1 commit
    • Alexis Imperial-Legrand's avatar
      runtime: explicit init of runtime-gdb helpers · 927b7ac3
      Alexis Imperial-Legrand authored
      If using other gdb python scripts loaded before Go's gdb-runtime.py
      and that have a different init prototype:
      Traceback (most recent call last):
        File "/usr/lib/go/src/pkg/runtime/runtime-gdb.py", line 446, in <module>
          k()
      TypeError: __init__() takes exactly 3 arguments (1 given)
      
      The problem is that gdb keeps all python scripts in the same namespace,
      so vars() contains them. To avoid that, load helpers one by one.
      
      R=iant, rsc
      CC=gobot, golang-dev
      https://golang.org/cl/9752044
      927b7ac3
  16. 29 Mar, 2013 1 commit
  17. 19 Nov, 2012 1 commit
  18. 13 Nov, 2012 1 commit
    • Russ Cox's avatar
      reflect: add ArrayOf, ChanOf, MapOf, SliceOf · 11209825
      Russ Cox authored
      In order to add these, we need to be able to find references
      to such types that already exist in the binary. To do that, introduce
      a new linker section holding a list of the types corresponding to
      arrays, chans, maps, and slices.
      
      To offset the storage cost of this list, and to simplify the code,
      remove the interface{} header from the representation of a
      runtime type. It was used in early versions of the code but was
      made obsolete by the kind field: a switch on kind is more efficient
      than a type switch.
      
      In the godoc binary, removing the interface{} header cuts two
      words from each of about 10,000 types. Adding back the list of pointers
      to array, chan, map, and slice types reintroduces one word for
      each of about 500 types. On a 64-bit machine, then, this CL *removes*
      a net 156 kB of read-only data from the binary.
      
      This CL does not include the needed support for precise garbage
      collection. I have created issue 4375 to track that.
      
      This CL also does not set the 'algorithm' - specifically the equality
      and copy functions - for a new array correctly, so I have unexported
      ArrayOf for now. That is also part of issue 4375.
      
      Fixes #2339.
      
      R=r, remyoudompheng, mirtchovski, iant
      CC=golang-dev
      https://golang.org/cl/6572043
      11209825
  19. 29 Feb, 2012 1 commit
  20. 01 Oct, 2011 1 commit
    • Russ Cox's avatar
      runtime: fix map memory leak · e7e5c5ad
      Russ Cox authored
      The map implementation was using the C idiom of using
      a pointer just past the end of its table as a limit pointer.
      Unfortunately, the garbage collector sees that pointer as
      pointing at the block adjacent to the map table, pinning
      in memory a block that would otherwise be freed.
      
      Fix by making limit pointer point at last valid entry, not
      just past it.
      
      Reviewed by Mike Burrows.
      
      R=golang-dev, bradfitz, lvd, r
      CC=golang-dev
      https://golang.org/cl/5158045
      e7e5c5ad
  21. 29 Sep, 2011 1 commit
  22. 23 Sep, 2011 1 commit
  23. 30 May, 2011 1 commit
  24. 14 Apr, 2011 1 commit
  25. 28 Mar, 2011 1 commit
  26. 20 Feb, 2011 1 commit
  27. 31 Jan, 2011 1 commit
  28. 15 Dec, 2010 1 commit
  29. 03 Dec, 2010 1 commit