[go-nuts] Delve v1.6.1 released

Hello Gophers! New Delve release day! Delve v1.6.1 is released today! This release contains 2 new commands, new options for existing commands, bug fixes and more! Check out the changelog for more details: https://github.com/go-delve/delve/blob/master/CHANGELOG.md#161-2021-05-18. -- You rece

[go-nuts] Delve v1.6.0 is released

Hello Gophers, Announcing the Delve v1.6.0 release! Thanks to everyone who contributed to this release! Notable changes: * Go 1.16 support * Apple M1 support * Syntax highlighting for code blocks (in terminal) * Bug fixes, performance improvements and more! Check out the full CHANGELOG here

[go-nuts] Delve v1.5.0

Announcing Delve v1.5.0! https://github.com/go-delve/delve/releases/tag/v1.5.0 Includes support for Go 1.15, new reload command, optimizations, bug fixes and more. Thanks to everyone who contributed to this release! -- You received this message because you are subscribed to the Google Groups

[go-nuts] Re: For a .net developer,how long it takes to learn go completely?

Depends on what you mean by completely. I was writing production Go code within 6 months after moving on from .NET. There are fundamental programming differences I found in the way you approach solutions. There is a lot to Go. I'm still learning after three years. I will never go back to .NET a

[go-nuts] Re: Im battling to understand pointers to strings in a function - Please help

I cleaned up the code a bit so that your function calls are working. The results are still not coming our correctly. Take another pass at the logic for inx(), and you should be able to get your solution working. Use slices instead of fixed length arrays. Also, you don't need to use reference po

[go-nuts] Delve v1.4.1 released!

Delve v1.4.1 is released! Thanks to everyone who contributed to this release! This release includes some new features, optimizations and bug fixes. Notable changes: * Support for linux/386 * DAP server initial release * New commands `display` and `examinemem` * Tracing improvements * Better sup

[go-nuts] Delve v1.4.0 released!

Hey Gophers, We've just released Delve v1.4.0 including new features, fixes and more! Check out the CHANGELOG for more details: https://github.com/go-delve/delve/blob/master/CHANGELOG.md#140-2019-02-11. Thanks to everyone who contributed during this release cycle! -- You received this message

[go-nuts] [HIRING] Software Engineer - LLVM & Go Toolchain

The Red Hat Platform Toolchain team is looking for a Software Engineer to join our engineering team working on the open source LLVM toolchain and its associated Clang (C and C++) front end or the Go toolchain. In this role, you will help investigate, contribute to, build, debug, and analyze thes

[go-nuts] Re: Any way to print a 'struct g' within delve/gdb

te: > > Hi Derek, > > Say I have the pointer value of a specific G struct, how to convert it to > 'struct g' (or any other form) in delve so that I can check > the details of its fields? > > For example (simply utilized runtime.m0.curg to get a pointer value here)

[go-nuts] Re: Any way to print a 'struct g' within delve/gdb

Can you reply with a gist showing the exact Delve commands you are attempting to use and what errors are being returned? There is some more information on the expression parser here . You can also open an issue on the Delv

[go-nuts] Delve v1.3.2

Hey Gophers! We are excited to announce the release of Delve v1.3.2! We have some new functionality and a bunch of fixes and improvements, so please check it out, test it out, and as always report any issues so we can continue making it better! You can read the full list of changes here: http

[go-nuts] Announcing Delve v1.3.0

Hey Gophers, The Delve team is excited to announce v1.3.0! Notable changes include: - Go 1.13 support - Initial FreeBSD support - Scripting interface via Starlark - Improved function call support - Ability to continue target immediately upon launch (useful for debugging within a container) - To

[go-nuts] Delve 1.2.0 released!

Hello all, Just wanted to announce the release of Delve 1.2.0! The major update here is Go 1.12 support, along with a bunch of new improvements and fixes. Read about the full release here: https://github.com/go-delve/delve/blob/master/CHANGELOG.md#120-2019-02-19. -- You received this message

[go-nuts] Delve 1.1.0 is released

Announcing Delve v1.1.0! Tons of fixes and improvements including: * Go 1.11 support * Initial support for function & method calls (still new, still improving) * New commands / options * Logging improvements * A lot more! Check out the full changelog here

Re: [go-nuts] where is an online version of older versions like 1.8 1.6 golang pkg doc ?

On Fri, Jan 19, 2018 at 10:07 AM, Ian Lance Taylor wrote: > Sounds like a good approach. Or I'm also open to someone writing the > necessary code for golang.org. I just started this approach simply serving static html files: https://golangdoc.github.io/pkg/1.10beta2/ https://golangdoc.github.io

Re: [go-nuts] where is an online version of older versions like 1.8 1.6 golang pkg doc ?

On Thu, Jan 18, 2018 at 7:39 PM, Ian Lance Taylor wrote: >> Like for Nodejs, and Python and many other language has permanent >> archived docs for olders versions: >> >> https://nodejs.org/docs/v8.4.0/api/http2.html is permanent URL for >> nodejs v8.4.0 >> >> https://nodejs.org/api/http2.html

[go-nuts] where is an online version of older versions like 1.8 1.6 golang pkg doc ?

like for 1.8 1.6 for archeology and other reasons, I am researching a in-house software written in Golang1.6 want an online version of golang1.6 doc? https://golang.org/doc/go1.6/pkg/encoding/json/ https://golang.org/pkg/encoding/json/ as I'm checking here is always pointing to latest version?

[go-nuts] Using visual C++ as the c compiler for CGo

Hi - I know this has been asked before, but I can't find a recent answer. Is it possible to use the visual studio compiler for cgo instead of gcc? If not, is there a project underway? If not, can someone point me to how I might contribute such a thing? Thanks -- You received this message be

[go-nuts] Re: delve

Hey, I'd be happy to answer any questions you have. On Monday, July 24, 2017 at 5:40:10 PM UTC-7, Robert Solomon wrote: > > Hi. I need help with using delve. Where should I direct my questions? > > I don't know where else to ask, so I'm asking here first. > > --rob solomon > > -- You recei

[go-nuts] Re: Delve v1.0.0-rc.1 release

Hey, Currently that is on our roadmap, but we do not have anybody committed to hacking on it. Ideally, either myself of my co-maintainer will have some time to tackle that, but we absolutely encourage help from the community for such a feature. If somebody would like to help with that work, mys

[go-nuts] Re: Delve v1.0.0-rc.1 release

Really glad that it's been a useful tool for you, always great to hear! On Tuesday, May 9, 2017 at 12:04:23 PM UTC-7, JuciÊ Andrade wrote: > > Derek, I want to say a big "thank you" to you and all people involved in > this project. > > Delve became an indispensible

[go-nuts] Re: Delve v1.0.0-rc.1 release

Really glad to hear it's been a useful tool for you, always great to hear! On Tuesday, May 9, 2017 at 12:04:23 PM UTC-7, JuciÊ Andrade wrote: > > Derek, I want to say a big "thank you" to you and all people involved in > this project. > > Delve became an indispen

[go-nuts] Re: Delve v1.0.0-rc.1 release

It _will_ be... eventually :). But not in this release unfortunately. On Monday, May 8, 2017 at 5:23:32 PM UTC-7, Gabriel Adumitrachioaiei wrote: > > Will it be possible to do function calls: > https://github.com/derekparker/delve/issues/119 > > > luni, 8 mai 2017, 19:42:43 UTC

[go-nuts] Delve v1.0.0-rc.1 release

Hey all, Just wanted to make some noise about the latest Delve release, v1.0.0-rc.1 . This is a particularly big release for us, and includes a bunch of fixes, improvements

[go-nuts] Re: LLDB only works for project contains one go source file

You could try using Delve for debugging: https://github.com/derekparker/delve On Wednesday, October 26, 2016 at 4:20:01 AM UTC-7, Leopold Freeman wrote: > > Hi: > I upgraded my MBP to macOS Sierra, and gdb was broke because Apple > tightened security policy. So I compiled LLDB from trunk acc

Re: [go-nuts] Re: Debugging in Go 1.8

> > But I found it hard to debug a Go program not started by delve itself. > When Delve compiles your program for you it passes `-gcflags="-N -l"`, which will produce a binary that's more suited for debugging. If you need to use `dlv exec` over `dlv debug`, you can build your binary using that

[go-nuts] Re: Debugging in Go 1.8

> And I'm sure the Delve developers are continuing to improve Delve. We are indeed. > I've mostly been comfortable with delve. Great! Hope it continues to work for you. We're constantly working to improve the debugging experience for Go, so feel free to reach out via our mailing list or Gith

[go-nuts] Re: Some best practices for debuging and optimizing with -gcflags?

FWIW Delve (https://github.com/derekparker/delve) sets the proper `gcflags` to produce a binary optimal for debugging if you need a debugger. On Monday, February 27, 2017 at 4:17:39 PM UTC-8, jamalsm...@gmail.com wrote: > > What are some best practices for general purpose -gcflags to use for >

Re: [go-nuts] Working Example of runtime.SetCgoSymbolizer?

rence now is that runtime.asmcgocall is listed as 'non-Go function', but that's probably because I happened to test with git master instead of 1.7. I look forward to testing more rigorously now. Cheers, - Derek -- You received this message because you are subscribed to the Google

Re: [go-nuts] Working Example of runtime.SetCgoSymbolizer?

y version for something the libbacktrace files uses (libgcc_s)? - Derek -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegrou

[go-nuts] Working Example of runtime.SetCgoSymbolizer?

aware it's labelled experiment, but perhaps Ian may comment. Mostly, I am asking on this list before I dive into the deep end and try and write my own handler, which will no doubt be a very large undertaking. - Derek [1] Example as follows: *crash.go*: package main /* void crash_now(int