Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

gprbuild V22.0.0 creates backtrace on incorrect input instead of error message

Open
#116 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
build-system

Research direction

Extract bug.tar.gz and reproduce the command from the issue in the AVRAda_Examples directory. Compare the current gprbuild 22.0.0 behavior with the older output, then trace the reported configuration-processing path. Done means incorrect input produces a user-facing error instead of an assertion backtrace.

Written by the indexing model from the issue text.

Description

calling gprbuild on the attached gpr-files creates a backtrace. Expand bug.tar.gz and go into AVRAda_Examples:

 ~/.config/alire/cache/dependencies/gprbuild_22.0.1_24dfc1b5/bin/gprbuild -s -j0 -p -P 7seg/seven_segment_disp.gpr
gprbuild: raised SYSTEM.ASSERTIONS.ASSERT_FAILURE : Invalid Id 0
[/home/re/.config/alire/cache/dependencies/gprbuild_22.0.1_24dfc1b5/bin/gprbuild]
0x8aab60 system__assertions__raise_assert_failure at ???
0x677161 gpr__names__get_name_string__5 at ???
0x5bfc61 gpr__conf__get_element_or_empty at ???
0x5c811f gpr__conf__get_or_create_configuration_file at ???
0x5c9d5b gpr__conf__process_project_and_apply_config at ???
0x5ca5d2 gpr__conf__parse_project_and_apply_config at ???
0x4a0430 _ada_gprbuild__main at ???
0x490bc4 main at ???
[/lib/x86_64-linux-gnu/libc.so.6]
0x7fdf8e6f9d08
[/home/re/.config/alire/cache/dependencies/gprbuild_22.0.1_24dfc1b5/bin/gprbuild]
0x490c18 _start at ???
0xfffffffffffffffe

gprbuild 18.0w (standard Debian version) gives a friendlier message, but still not very helpful:

gprbuild -s -j0 -p -P 7seg/seven_segment_disp.gpr
gprbuild: raised CONSTRAINT_ERROR : gpr-names.adb:231 range check failed
Dominant language
Ada
Stars
81
Forks
24
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AdaCore/gprbuild

All issues in AdaCore/gprbuild

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.