-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDL_LoadObject error message truncated to 128 bytes long #5795
Comments
Also just randomly ran into this; independently of takase1121 (though we do randomly work on the same project). |
Seems like this can be changed by modifying the
line in SDL_error.c.h. I'm assuming there's a reason this is so low. Would SDL be open to doubling, or quadrupling this number? |
Previous commit fix an error, I got an error when the error message is reallocated.
|
probably the same patch here: cbd0187#diff-c9d13ae3458a7283597823c15d420ae5bfe15ff45ece5c6d51930df6b0e2f0f7L72 ? |
Applied the same pattern. Anyway the code is not compiled because of |
Also added SDL_GetOriginalMemoryFunctions() Fixes libsdl-org#5795
…SDL error message) (see libsdl-org#5795)
I'm working on a program that uses
SDL_LoadObject
to load a SO file. However, an error occured and I can't see the full error message because the SO file path is too long and obscured most of the error message.SDL_SetError()
seems to have a 128 byte limit.Error message:
Failed loading /home/takase/.luarocks/lib64/lua/5.4/ltreesitter.so: /home/takase/.luarocks/lib64/lua/5.4/ltreesitter.so: undefi
You can see that the string is truncated to 127 bytes.
I suggest to omit filenames in the error message. In this case,
dlerror()
somehow appends the filename and causes wastage.The text was updated successfully, but these errors were encountered: