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

proc: do not ignore error return of funcCallEvalFuncExpr #3850

Merged
merged 1 commit into from
Nov 6, 2024

Conversation

aarzilli
Copy link
Member

@aarzilli aarzilli commented Nov 6, 2024

This is probably the cause of the panic such as in issue #3848 and
other similar issues, it is hard to be sure because we never get a
proper reproducer but judging from the stack traces it should be this.

Also it doesn't affect versions of Go that have the debug pinner.

Fixes #3848

This is probably the cause of the panic such as in issue go-delve#3848 and
other similar issues, it is hard to be sure because we never get a
proper reproducer but judging from the stack traces it should be this.
Also it doesn't affect versions of Go that have the debug pinner.

Fixes go-delve#3848
Copy link
Member

@derekparker derekparker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekparker derekparker merged commit b16e12f into go-delve:master Nov 6, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

invalid memory address or nil pointer dereference panic from delve package
2 participants