Skip to content

Conversation

@LeFrosch
Copy link
Collaborator

@LeFrosch LeFrosch commented Nov 28, 2025

Followup for: #7825, #7639 and #7827

Introduces a common flag builder for assembling all flags required for debug builds / runs. In theory we would like a builder that creates BlazeCommand and hands this off the the BazelExecService to have full control over the environment, but this would be a major refactor.

@LeFrosch LeFrosch force-pushed the pull/7f975bb3f99b2f6ba1b664b42f93933a45b2bd5b branch from 7f975bb to a64dcbc Compare November 28, 2025 09:49
@LeFrosch LeFrosch linked an issue Nov 28, 2025 that may be closed by this pull request
@LeFrosch LeFrosch marked this pull request as ready for review November 28, 2025 10:52
@github-actions github-actions bot added product: CLion CLion plugin awaiting-review Awaiting review from Bazel team on PRs labels Nov 28, 2025
@LeFrosch LeFrosch linked an issue Dec 1, 2025 that may be closed by this pull request
Copy link
Collaborator

@ujohnny ujohnny left a comment

Choose a reason for hiding this comment

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

overall looks good, do we want to add debug test as I did in #7825 ?

compilerKind,
OS.CURRENT,
withClangTrimPaths = Registry.`is`("bazel.trim.absolute.path.disabled"),
withFissionFlag = Registry.`is`("bazel.clwb.debug.fission.disabled"),
Copy link
Collaborator

Choose a reason for hiding this comment

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

I guess we have to have ! here as then

 && withFissionFlag) {
      switchBuilder.withSwitch("--fission=yes")
    }

}
}

fun withTestFlags(timeout: Int? = 3600) {
Copy link
Collaborator

@ujohnny ujohnny Dec 3, 2025

Choose a reason for hiding this comment

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

60.minutes and later toSeconds()

*/
class BazelDebugFlagsBuilder(
private val debuggerKind: BlazeDebuggerKind,
private val compilerKind: OCCompilerKind,
Copy link
Collaborator

Choose a reason for hiding this comment

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

some compilerkind/debuggerkind combinations do not make any sense, do we want to enforce some checks here or around?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-review Awaiting review from Bazel team on PRs product: CLion CLion plugin

Projects

Status: Untriaged

Development

Successfully merging this pull request may close these issues.

Breakpoints not hit in CLion May be bazel plugin or cmake bug.

2 participants