# New Issue: Better halting error message with ROCm 6.3

**URL:** <https://chapel.discourse.group/t/new-issue-better-halting-error-message-with-rocm-6-3/47823>\
**Category:** Issues\
**Created:** [February 18, 2026, 12:28am UTC](https://chapel.discourse.group/t/new-issue-better-halting-error-message-with-rocm-6-3/47823 "2026-02-18T00:28:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jabraham17](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@jabraham17](https://chapel.discourse.group/u/jabraham17)\
**Post date:** [February 18, 2026, 12:28am UTC](https://chapel.discourse.group/t/new-issue-better-halting-error-message-with-rocm-6-3/47823/1 "2026-02-18T00:28:50Z")

</div>

28415, "jabraham17", "Better halting error message with ROCm 6.3", "2026-02-18T00:27:35Z"

> <https://github.com/chapel-lang/chapel/issues/28415>
>
> Currently, when using ROCm 6.3 with Chapel, we get bad error messages when a hal…t occurs (like for example when using \`@assertOnGpu\`)
> 
> Its not clear if the error is on our side with how we use ROCm or a ROCm bug (we did not have this issue with previous ROCm versions)
> 
> For example
> \`\`\`chapel
> @assertOnGpu
> foreach i in 1..10 { }
> \`\`\`
> 
> When running this code, instead of seeing a nice halt message, users will likely see segfault or some other unclear halt when hitting the halt. Since this is an error condition anyways, its not terrible that Chapel programs crash when halting. But it would be nice to have better errors.
> 
> This issue serves as a place to request that we have better halt messages for the latest versions of ROCm
> 
> 
> PR https://github.com/chapel-lang/chapel/pull/28220 adds support for ROCm 6.3, but does not fix these bad error messages. https://github.com/chapel-lang/chapel/issues/26934 has some more information on this topic

Currently, when using ROCm 6.3 with Chapel, we get bad error messages when a halt occurs (like for example when using `@assertOnGpu`)

Its not clear if the error is on our side with how we use ROCm or a ROCm bug (we did not have this issue with previous ROCm versions)

For example

```chapel
@assertOnGpu
foreach i in 1..10 { }

```

When running this code, instead of seeing a nice halt message, users will likely see segfault or some other unclear halt when hitting the halt. Since this is an error condition anyways, its not terrible that Chapel programs crash when halting. But it would be nice to have better errors.

This issue serves as a place to request that we have better halt messages for the latest versions of ROCm

PR [Add support for ROCm 6.3 by jabraham17 · Pull Request #28220 · chapel-lang/chapel · GitHub](https://github.com/chapel-lang/chapel/pull/28220) adds support for ROCm 6.3, but does not fix these bad error messages. [ROCm 6.3 support · Issue #26934 · chapel-lang/chapel · GitHub](https://github.com/chapel-lang/chapel/issues/26934) has some more information on this topic