debuggable installations in eic/containers: wire --debug-source and --debug-symbols into the dbg environment - #388
Conversation
|
@SebastianPaucar In master (#393) we added a mirror for the source that has the ssl certificate errors in CI here. |
Branch updated with #393. Also implemented OCI push/autopush (per |
Noticed some of the newer cherry-picks in |
|
It seems this PR has created a whole new spack build cache at https://eicweb.phy.anl.gov/containers/eic_container/container_registry/154 because we reuse the branch name as container registry name ;-) |
…in dbg/spack.yaml
for more information, see https://pre-commit.ci
…ype. spack.sh: cherry-pick full debuggable framework
44d8e6f to
2085e60
Compare
This PR adds the framework related to the following design discussion for debuggable installations in spack packages:
spack/spack): DWARF-referenced source hook and symbol splitting plus GDB init for debuggable installations.spack/compiler-wrapper):-ffile-prefix-map=<staging>=.and--build-idinjection in compiler-wrapper.spack/spack-packages): setSPACK_DEBUG_PREFIX_MAPfor-ffile-prefix-map=<stage>=.injection at compiler-wrapper level.(
SebastianPaucar/spack):--debug-sourceand--debug-symbolsPoC container demo (verified end-to-end).In summary, this PR adds
--debug-sourceand--debug-symbolsto spack install whenENV=dbg, via a new conditional inscripts/build-eic.shthat appends toSPACK_INSTALL_FLAGS.Worth noting:
SPACK_INSTALL_FLAGSis also read by the runtime--use-buildcache onlyinstall stages, so these flags will currently reach install-from-buildcache too, not just fresh builds.