Skip to content

build(make): emit cc65 debug info (-g + --dbgfile) for PRG - #44

Merged
JC-000 merged 1 commit into
masterfrom
dbgfile-build-v2
May 17, 2026
Merged

build(make): emit cc65 debug info (-g + --dbgfile) for PRG#44
JC-000 merged 1 commit into
masterfrom
dbgfile-build-v2

Conversation

@JC-000

Copy link
Copy Markdown
Owner

Summary

  • Add --dbgfile build/c64-https.dbg to the main ld65 link.
  • Ensure -g is set on ca65 invocations across the integration shell scripts that exist on master.
  • PRG bytes are bit-identical (sha256 verified in the original commit on the Phase-5 development branch).
  • VICE monitor and diagnostic tools can consume the .dbg directly for PC->symbol/source mapping.

Overlay-specific --dbgfile additions (for build/lib/overlay-p384-{sha384,curve}.dbg) will land alongside the P-384 overlay infrastructure in a separate PR.

Test plan

  • Incremental make BACKEND=uci succeeds with no warnings
  • build/c64-https.dbg is emitted and parses as cc65 dbg format
  • PRG sha256 matches a pre-change build
  • Idempotent build (second make is a no-op)

🤖 Generated with Claude Code

Adds --dbgfile build/c64-https.dbg to the main ld65 link and ensures
-g is set on ca65 invocations. PRG bytes are bit-identical with -g
enabled; the .dbg sidecar is purely additive.
VICE monitor and diagnostic tools can consume the .dbg directly for
PC -> symbol/source mapping, eliminating the need to grep labels.txt
for symbol resolution. Per-overlay .dbg files will ride along with
the P-384 overlay work in a separate PR.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for freeto 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.

1 participant

@JC-000