Add ggml_abort callback function to handle errors - #244
Merged
Conversation
Apparently whisper.cpp has the ability to set a callback function that is called when there's an error in the GGML processing. It's poorly (not at all) documented, and seems to take a string argument, though the parameter is always `null` when it's been called, but having it set seems to prevent some crashes... somehow?? I guess it expects there to be one, so if there isn't we get a null pointer exception
Tabby
force-pushed
the
add-ggml-abort-callback
branch
from
October 23, 2025 23:13
169d866 to
bdf0f5a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Apparently whisper.cpp has the ability to set a callback function that is called when there's an error in the GGML processing. It's poorly (not at all) documented, and seems to take a string argument, though the parameter is always
nullwhen it's been called, but having it set seems to prevent some crashes... somehow?? I guess it expects there to be one, so if there isn't we get a null pointer exception