RelView.py does not recognise modern sdcc output
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
RelView.is_valid_for_data() requires b"XL2\n" and b"\nO -mz80\n", but sdcc 4.6 emits XL4 and O -mz80 sdcccall(1), so current object files are never detected.
The ^T (.. ..) record regex also assumes 2-byte addresses, while XL4 T records carry 4-byte addresses.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in RelView.py at RelView.is_valid_for_data() and the ^T record regex. Compare the current checks with the sdcc 4.6 output described in the issue, including XL4, sdcccall(1), and four-byte T-record addresses. Done means current sdcc object files are recognised and their T records are handled correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100