Skip to content

Conversation

@plemarquand
Copy link
Contributor

This will help diagnose the failure to find LLDB on Windows 6.2

Tasks

  • Required tests have been written
  • Documentation has been updated
  • Added an entry to CHANGELOG.md if applicable

): Promise<Result<string>> {
let executable: string;
try {
executable = await toolchain.getLLDB();
Copy link
Contributor

Choose a reason for hiding this comment

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

while we're here, maybe a debug log of what was found

logger?.error(`Failed to get LLDB library path for lldb on Windows, error: ${error}`);
return Result.makeFailure(undefined);
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Can't seem to add comment to lines not in patch, but in findLibLLDB can we add debug logging for which folders we try to find it in, and debug result of await findLibLLDB(pathHint)

Copy link
Contributor

Choose a reason for hiding this comment

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

Also don't think it would be too verbose to log directory contents returned by readdir in findFileByPattern

@award999
Copy link
Contributor

Some suggestions of how we could taker debug logging even further

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.

2 participants