Skip to content
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

Support for _set_thread_local_invalid_parameter_handler? #944

Open
johnsonjh opened this issue Jul 30, 2023 · 3 comments
Open

Support for _set_thread_local_invalid_parameter_handler? #944

johnsonjh opened this issue Jul 30, 2023 · 3 comments

Comments

@johnsonjh
Copy link

Is it possible to support _set_thread_local_invalid_parameter_handler?

@LADSoft
Copy link
Owner

LADSoft commented Jul 30, 2023

I will have to see what it does... give me a day or two on this...

@johnsonjh
Copy link
Author

No rush - consider this a low-priority request. There are details at https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/set-invalid-parameter-handler-set-thread-local-invalid-parameter-handler?view=msvc-170 and links to some of the related functions (the _get… function, and the non-thread-local variants, etc.)

It seems (if I understand https://github.com/MicrosoftDocs/cpp-docs/blob/main/docs/c-runtime-library/reference/set-invalid-parameter-handler-set-thread-local-invalid-parameter-handler.md correctly) that this function is available in classic MSVCRT as well as UCRT, so hopefully it's simple.

@LADSoft
Copy link
Owner

LADSoft commented Jul 31, 2023

adding this function itself is easy, however, adding the functionality that it needs cuts across a lot of other runtime functions so it becomes somewhat involved. I have to research which functions are affected. If it affects things like strlen() or memcpy() as well I may only be able to do a partial implementation for now, as we are going to be rewriting a lot of the assembly language code to make it more portable, when we start supporting for example the x64 processor. That said, I'm trying to get #344 and #168 done so I can have a release to support #603, so this is going to be somewhat delayed...

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

No branches or pull requests

2 participants