Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Debug: Improve 'bad access' error message #3196

Merged
merged 1 commit into from
Apr 25, 2020

Conversation

polinasok
Copy link
Contributor

Clarify the error message that is printed to the user when delve returns "bad access".
Updates #1903.

}

logError(message + ' - ' + errorMessage);

if (errorMessage === 'bad access') {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This never gets printed because by the time we get to this line, 'bad access' has already been wiped out by the previous statements. I don't think this message is necessary - the stack trace is printed with "last known" comment, which implies that it might not be the expected most recent state.

Copy link
Contributor

@quoctruong quoctruong left a comment

Choose a reason for hiding this comment

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

LGTM!

@polinasok
Copy link
Contributor Author

cc @lggomez
cc @jhendrixMSFT

@lggomez
Copy link
Contributor

lggomez commented Apr 22, 2020

LGTM

@ramya-rao-a ramya-rao-a merged commit 740d7eb into microsoft:master Apr 25, 2020
@ramya-rao-a
Copy link
Contributor

The latest update 0.14.2 has this change, Thanks @polinasok

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

Successfully merging this pull request may close these issues.

5 participants