ADA.IO_EXCEPTIONS.NAME_ERROR when executing Svd2Ada
Open
Nobody has claimed this yet.
- Dominant language
- Ada
- Stars
- 71
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
I installed Svd2Ada using Alire's install command. Here's the output of where it installed it:
alr install --info
Installation prefix found at /Users/Joe/.alire
Contents:
svd2ada=0.1.0
xmlada=22.0.0
xtensa_dynconfig=0.1.0-dev
To use the program, I exported Alire's installation location. When I execute svd2ada on a SVD file, I get the following error:
svd2ada --package=esp32s3.svd --gen-interrupts --no-uint-subtypes ../svd/esp32s3.svd --output=../esp32s3_svd
Execution of svd2ada terminated by unhandled exception
raised ADA.IO_EXCEPTIONS.NAME_ERROR : Could not open /Users/Joe/.alire/schema/CMSIS-SVD_Schema_1_3_1.xsd
Load address: 0x104cbc000
Call stack traceback locations:
0x104e6e31c 0x104e6e37c 0x104e5dbb0 0x104cbf4d0 0x104cc034c 0x104ec173c
The file doesn't exist
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 reported svd2ada command and inspect the Alire installation under /Users/Joe/.alire, especially the missing schema/CMSIS-SVD_Schema_1_3_1.xsd path. Determine why the installed command cannot access that schema, then rerun the same command against ../svd/esp32s3.svd; done means it no longer raises ADA.IO_EXCEPTIONS.NAME_ERROR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100