Svd2Ada doesn't properly resolve relative paths pass in as Output_Dir
Nobody has claimed this yet.
- Dominant language
- Ada
- Stars
- 71
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Svd2Ada doesn't resolve the Output_Dir if it's a relative path, leading to an GNAT.DIRECTORY_OPERATIONS error. This happens on MacOS X, but not sure about any of other platforms as I haven't tested it.
svd2ada "LPC176x5x.svd" --boolean -o "../../src" -p svd --base-types-package HAL --gen-uint-always
a_0.1.0_6eb0b591/bin/svd2ada terminated by unhandled exception
raised GNAT.DIRECTORY_OPERATIONS.DIRECTORY_ERROR : g-dirope.adb:617
Load address: 0x10b398000
Call stack traceback locations:
0x10b56b5f4 0x10b405ad0 0x10b4803c8 0x10b39a09d 0x10b5ec03c
Contributor guide
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
Reproduce the issue through the svd2ada entry point with the shown command and relative Output_Dir. Trace how that path is handled before GNAT.DIRECTORY_OPERATIONS raises DIRECTORY_ERROR, then verify the same command completes successfully with a relative output path on macOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100