Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't debugging on macOS Sequoia #3812

Closed
ZenkieBear opened this issue Sep 19, 2024 · 13 comments
Closed

Can't debugging on macOS Sequoia #3812

ZenkieBear opened this issue Sep 19, 2024 · 13 comments

Comments

@ZenkieBear
Copy link

ZenkieBear commented Sep 19, 2024

Please answer the following before submitting your issue:
I updated my macOS to Sequoia yesterday. Now I can't debugging through VSCode or GoLand, and their console all printed Warning: no debug info found, some functionality will be missing such as stack traces and variable evaluation..

Note: Please include any substantial examples (debug session output,
stacktraces, etc) as linked gists.
image

If this is about source listing not showing up (or breakpoints not being
accepted) while running in a container please read our
FAQ
first.

  1. What version of Delve are you using (dlv version)? 1.21.2
  2. What version of Go are you using? (go version)? 1.21.6
  3. What operating system and processor architecture are you using? macOS Sequoia/Apple Silicon M2
  4. What did you do? Update macOS from Sonoma to Sequoia(15.0)
  5. What did you expect to see? The debugging program works right.
  6. What did you see instead? When I started debugging my program, the breakpoints began gray circles from red dots.
image
@codeblooded
Copy link

This is broken for me also.

@jay-youngn
Copy link

jay-youngn commented Sep 19, 2024

Failed to launch: could not launch process: error reading debug_info: decoding dwarf section info at offset 0x5c2bd9: DW_FORM_strx with no .debug_str_offsets section


Version: 1.93.1
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.0.0

@twz915
Copy link

twz915 commented Sep 19, 2024

@jay-youngn
Copy link

mattn/go-sqlite3#1269 (comment)

➜ go install github.com/go-delve/delve/cmd/dlv@master
go: downloading github.com/go-delve/delve v1.23.1-0.20240918211707-059f149433c1

It works! Thx, old iron

@aarzilli
Copy link
Member

This is a duplicate of #3797 (but I'm going to leave it open for a while so people don't open more duplicates)

@RogelioLozano
Copy link

Hi,

I've already seen #3797 and used the latest master branch to try to make dlv work in my case; nevertheless, I'm still getting the following error when executing

dlv debug .

Screenshot 2024-09-20 at 12 24 05 p m

Obviously same problem show up in vscode.

What version of Delve are you using (dlv version)?
Screenshot 2024-09-20 at 12 26 34 p m

What version of Go are you using? (go version)?
Screenshot 2024-09-20 at 12 26 53 p m

What operating system and processor architecture are you using? macOS Sonoma 14.7 Apple Silicon M3 Pro

What did you do? Update macOS to latest version allowed

Previously it was working flawlessly. I use dlv very much, so I'm concerned to make it work again.

@mfamador
Copy link

mfamador commented Sep 22, 2024

Hi, running the current master version of dlv on a project using go1.23.1 the fix from #397 seems to work.
But on another project using go1.22.5 I still get the error:

❯ ~/go/bin/dlv debug cmd/main.go
Warning: no debug info found, some functionality will be missing such as stack traces and variable evaluation.                           
could not launch process: could not read debug info (decoding dwarf section info at offset 0x0: too short) and could not read go symbol table (could not find rodata struct member)

@ZenkieBear
Copy link
Author

Hi, running the current master version of dlv on a project using go1.23 the fix from #397 seems to work. But on another project using go1.22.5 I still get the error:

❯ ~/go/bin/dlv debug cmd/main.go
Warning: no debug info found, some functionality will be missing such as stack traces and variable evaluation.                           
could not launch process: could not read debug info (decoding dwarf section info at offset 0x0: too short) and could not read go symbol table (could not find rodata struct member)

Yes, I did upgrade my golang to v1.23.0(from 1.21.0). The problem resolves.

@mfamador
Copy link

Should this issue be closed? Shouldn't older versions work as well?

@ZenkieBear ZenkieBear reopened this Sep 23, 2024
@ZenkieBear
Copy link
Author

After updating go and dlv version, my program crumbs while debugging, and printed "not implemented".

@plopezlpz
Copy link

what about older go versions?

@ZenkieBear
Copy link
Author

what about older go versions?

The latest go version works well for me.

@funwithbots
Copy link

fwiw, when I updated go to v1.23.2, dlv stayed broken on master which still seems to point to v1.23.0. I had to install delve v1.23.1 using
go install github.com/go-delve/delve/cmd/@v1.23.1
to fix this error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants