[go-nuts] Delve v1.6.1 released

[Derek Parker]

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 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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/46c56a73-993b-4934-b601-c7620cd73d06n%40googlegroups.com.

[go-nuts] Delve v1.6.0 is released

[Derek Parker]

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 
.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/fb909311-a7f0-4cf2-8503-8856a7ea38c8n%40googlegroups.com.

[go-nuts] Delve v1.5.0

[Derek Parker]

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 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/64a1b56e-62e9-4842-af65-f677c44b74f1o%40googlegroups.com.

[go-nuts] Delve v1.4.1 released!

[Derek Parker]

 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 support for debugging CLI apps
... & more.

For more information and more complete list of changes, check out the tag 
on GitHub and the change list:

https://github.com/go-delve/delve/releases/tag/v1.4.1

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/300552eb-6889-41f9-8395-a84f3856855f%40googlegroups.com.

[go-nuts] Delve v1.4.0 released!

[Derek Parker]

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 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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/e3a3ef22-c23c-4954-b056-985cd364455e%40googlegroups.com.

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

[Derek Parker]

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 these 
and related tools.

https://us-redhat.icims.com/jobs/75775/software-engineer---llvm-%26--go-toolchain/job

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/55961da4-9630-48b2-abdb-981417286571%40googlegroups.com.

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

[Derek Parker]

If you look at the output of your first command you see the result 
`(**runtime.g)()`, however you're trying to cast to 
`(runtime.g*)()`. The correct syntax you're looking for is 
` *(*runtime.g)()`. Hope that helps!

On Monday, November 11, 2019 at 11:29:42 PM UTC-8, Xiangdong JI wrote:
>
> 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)
>
> (dlv) p &runtime.m0.curg
> (**runtime.g)(0x56a140)
>
> Just tried a few commands to convert the value back to 'struct g' or a 
> pointer to 'struct g'
>
> (dlv) p (runtime.g*)(0x56b140)
> Command failed: 1:12: expected operand, found ')'
> (dlv) p ('runtime.g'*)(0x56b140)
> Command failed: 1:2: illegal rune literal
> (dlv) p ("runtime.g"*)(0x56b140)
> Command failed: 1:14: expected operand, found ')'
> (dlv) p ("runtime".g*)(0x56b140)
> Command failed: 1:14: expected operand, found ')'
>
> Thanks.
>
> On Tuesday, November 12, 2019 at 2:28:12 AM UTC+8, Derek Parker wrote:
>>
>> 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 
>> <https://github.com/go-delve/delve/blob/master/Documentation/cli/expr.md>. 
>> You can also open an issue on the Delve Github repo and we can help you out 
>> over there as well.
>>
>> On Sunday, November 10, 2019 at 11:58:24 PM UTC-8, Xiangdong JI wrote:
>>>
>>> Given a valid goroutine structure's pointer, say retrieving from the 
>>> register 'g', how can I convert it to 'struct g' in delve or gdb?
>>>
>>> gdb usually reports "A syntax error in expression ...", and delve issues 
>>> various "Command failed" message (failed to figure the proper way of 
>>> converting a literal, I guess).
>>>
>>> Thanks.
>>>
>>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/8a62a611-9e83-4a2b-9751-e943d99df128%40googlegroups.com.

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

[Derek Parker]

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 Delve Github repo and we can help you out 
over there as well.

On Sunday, November 10, 2019 at 11:58:24 PM UTC-8, Xiangdong JI wrote:
>
> Given a valid goroutine structure's pointer, say retrieving from the 
> register 'g', how can I convert it to 'struct g' in delve or gdb?
>
> gdb usually reports "A syntax error in expression ...", and delve issues 
> various "Command failed" message (failed to figure the proper way of 
> converting a literal, I guess).
>
> Thanks.
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/b22ba5be-425b-46be-82e4-099417969f5d%40googlegroups.com.

[go-nuts] Delve v1.3.2

[Derek Parker]

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: https://github.com/go-delve/delve/blob/master/CHANGELOG.md#132-2019-10-21.

Thanks to everyone who contributed to this release!

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/861993bf-0450-4a23-a6e5-d80083cebc3d%40googlegroups.com.

[go-nuts] Announcing Delve v1.3.0

[Derek Parker]

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)
- Tons more features, fixes and improvements!

Full changelog available here: 
https://github.com/go-delve/delve/blob/master/CHANGELOG.md#130-2019-08-27.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/dd31e0ae-3875-4e12-a252-ff8baf1339dc%40googlegroups.com.

[go-nuts] Delve 1.2.0 released!

[Derek Parker]

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 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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] Delve 1.1.0 is released

[Derek Parker]

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 

.

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] Re: delve

[Derek Parker]

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 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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Derek Parker]

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, myself 
or my co-maintainer would be happy to point them in the right direction of 
where to get started.

On Thursday, May 11, 2017 at 11:18:56 AM UTC-7, Christian LeMoussel wrote:
>
> Hi,
>
> When can we expect the release for 32 bit system ?
>

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Derek Parker]

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 tool for me. I feel much safer after 
> executing new code step by step, and I am sure I am not alone.
>
> I owe you one, guys.
>
>

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Derek Parker]

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 indispensible tool for me. I feel much safer after 
> executing new code step by step, and I am sure I am not alone.
>
> I owe you one, guys.
>
>

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Derek Parker]

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+1, Derek Parker a scris:
>>
>> Hey all,
>>
>> Just wanted to make some noise about the latest Delve 
>> <https://github.com/derekparker/delve> release, v1.0.0-rc.1 
>> <https://github.com/derekparker/delve/blob/master/CHANGELOG.md#100-rc1-2017-05-05>
>> .
>>
>> This is a particularly big release for us, and includes a bunch of fixes, 
>> improvements and new features. I'll break down the new features shortly, 
>> but just wanted to call out this is an exciting milestone for the project, 
>> and we're excited to be driving towards a 1.0.0 release. What does that 
>> mean to you as a user? Well, not much should change, the project has been 
>> pretty stable, we have had API compatibility guarantees for a while now, 
>> etc, so this release is mostly symbolic. It does not mean the project is 
>> feature complete, we will be working hard to continue to add new features, 
>> support for more systems, and overall improvements as usual.
>>
>>  For a full list of changes, please check out the changelog 
>> <https://github.com/derekparker/delve/blob/master/CHANGELOG.md#100-rc1-2017-05-05>,
>>  
>> but I wanted to highlight some interesting features:
>>
>> Ability to swap low-level back ends. This means you can select either the 
>> native Delve back end, gdbserver, lldb-server, or Mozilla RR. The most 
>> exciting of this, in my opinion, is the ability to use the Mozilla RR (
>> http://rr-project.org/) project as a back end. This allows for record & 
>> replay deterministic debugging, and allows you to combine the power of 
>> Delve and RR into a very useful debugging tool for Go.
>>
>> Lastly, would just like to say thanks to the community overall for the 
>> support of the project and for all the patches, bug reports submitted 
>> editor integrations, etc, and co-maintainer Alessandro 
>> <https://github.com/aarzilli> for all the help, fixes, improvements, 
>> reviews and so on.
>>
>> Please check out this release, file bugs, and look out for the v1.0.0 
>> release within the coming weeks!
>>
>

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Derek Parker]

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 and new features. I'll break down the new features shortly, 
but just wanted to call out this is an exciting milestone for the project, 
and we're excited to be driving towards a 1.0.0 release. What does that 
mean to you as a user? Well, not much should change, the project has been 
pretty stable, we have had API compatibility guarantees for a while now, 
etc, so this release is mostly symbolic. It does not mean the project is 
feature complete, we will be working hard to continue to add new features, 
support for more systems, and overall improvements as usual.

 For a full list of changes, please check out the changelog 
,
 
but I wanted to highlight some interesting features:

Ability to swap low-level back ends. This means you can select either the 
native Delve back end, gdbserver, lldb-server, or Mozilla RR. The most 
exciting of this, in my opinion, is the ability to use the Mozilla RR 
(http://rr-project.org/) project as a back end. This allows for record & 
replay deterministic debugging, and allows you to combine the power of 
Delve and RR into a very useful debugging tool for Go.

Lastly, would just like to say thanks to the community overall for the 
support of the project and for all the patches, bug reports submitted 
editor integrations, etc, and co-maintainer Alessandro 
 for all the help, fixes, improvements, 
reviews and so on.

Please check out this release, file bugs, and look out for the v1.0.0 
release within the coming weeks!

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Derek Parker]

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 according to here 
>  and here . 
> Here are the steps:
>
> > svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
> > cd llvm/tools
> > svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
> > svn co http://llvm.org/svn/llvm-project/lldb/trunk lldb
> > cd clang/tools
> > svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk 
> clang-tools-extra
> > cd ../../../projects
> > svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt
> > svn co http://llvm.org/svn/llvm-project/libcxx/trunk libcxx
> > svn co http://llvm.org/svn/llvm-project/libcxxabi/trunk libcxxabi
> > svn co http://llvm.org/svn/llvm-project/libunwind/trunk libunwind
> > svn co http://llvm.org/svn/llvm-project/lld/trunk lld
> > cd .. && mkdir build && cd build
> > cmake .. -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX="$INSTALL_DIR"/llvm-
> "$1" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_DOXYGEN=Off 
> -DLLVM_ENABLE_SPHINX=Off
>
> The lldb I compiled only works for simple project contains one go source 
> file. If the project contains many go files (go build with -gcflags "-N 
> -l"), the outputs of lldb were all assembly codes:
>
> > lldb ./bin/debug/xkcd 
>
> (lldb) target create "./bin/debug/xkcd"
>
> Current executable set to './bin/debug/xkcd' (x86_64).
>
> (lldb) b main.main
>
> Breakpoint 1: where = xkcd`main.main + 77 at xkcd.go:16, address = 
> 0x208d
>
> (lldb) r
>
> Process 38114 launched: './bin/debug/xkcd' (x86_64)
>
> Process 38114 stopped
>
> * thread #6: tid = 0x0001, 0x208d libenergytrace.dylib, stop 
> reason = breakpoint 1.1
>
> frame #0: 0x208d libenergytrace.dylib
>
> ->  0x208d: callq  0x5d4a0
>
> 0x2092: movq   0x366ccf(%rip), %rax
>
> 0x2099: jmp0x209b
>
> 0x209b: movzbl (%rax), %eax
>
>
> It seems llvm supports go from v3.8 (
> https://groups.google.com/forum/#!topic/golang-nuts/pzpNcarQcvo).
>
> So, did I miss some compile options?
>
>
>
>

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Derek Parker]

>
> 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 
flag and you should have a better experience.

On Wednesday, March 1, 2017 at 7:59:54 PM UTC-8, Nyah Check wrote:
>
> Hi JuciE,
>  
>
>> Nyah, there are several IDEs capable of controlling Delve under the hood 
>>> to debug Go programs. It works nicely.
>>> If you are used to Visual Studio you will feel in home with VSCode. Even 
>>> shortcuts for debugging are the same.
>>>
>>>  
> I can't say much about IDEs since I don't really use them much. Tried 
> Atom, it was too slow for my system. I just stuck with Emacs and gedit 
> while running delve from my terminal. I don't currently know the recent 
> updates to delve. But I found it hard to debug a Go program not started by 
> delve itself. Since most of the functions and goroutines seen in the 
> debugger were not the implemented functions of my source code. I don't know 
> if anyone had that experience.
>
> Thanks,
>

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] Re: Debugging in Go 1.8

[Derek Parker]

> 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 Github if you run into any issues or have any ideas for 
improvement.

On Wednesday, March 1, 2017 at 5:41:56 AM UTC-8, Nyah Check wrote:
>
> I'm currently reading the Go 1.8 release documentation; I've not seen any 
> additional tools to facilitate Go debugging. I've mostly been comfortable 
> with delve. But I just wish to know if the golang-devs have any plans of 
> upgrading the go debugger? GDG sucks for me already.
>
> Thanks,
> Nyah
>
> -- 
> "The heaviest penalty for declining to rule is to be ruled by someone 
> inferior to yourself." --*Plato* 
>

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Derek Parker]

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 
> debugging and conversely for optimizing code?
>

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.