Skip to content

Conversation

@willyborn
Copy link
Contributor

The unified version of arrayfire, an std::exception is throw while collecting the arrayfire global error message.
Now the arrayfire error message is collected from the correct platform, resulting in the throwing of an af::exception filled with info.

When checking the unified tests: 18 tests failed because an unexpected exception was thrown

Description

When collecting the error message from the underlying platform, the address of the corresponding function was incorrect, resulting in an access violation.
Result:

  • Yes, an exception was thrown
  • No, af::exception was not thrown, so no info on the real error

Fixes: #3276 #2346

Changes to Users

None

Checklist

  • Rebased on latest master
  • Code compiles
  • Tests pass
  • Functions added to unified API
  • Functions documented

Copy link
Contributor

@christophe-murphy christophe-murphy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, thanks!

@christophe-murphy christophe-murphy merged commit 4d5954d into arrayfire:master Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Program crash with no error message when using Unified Backend af.lib

2 participants