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
Put error global variables into thread-local storage #112
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking more about this, shouldn't we reset
err->code = 0
here? Otherwise, the check below in line 460 will fail if this function is called after another function that has seterr->code
.Going one step further, perhaps when in
TLS_ERROR_RESET_LAST
mode, we should always seterr->code = 0
. Or is there a case where we want to reset one of the error codes, but not the other?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good point, thank you very much!
I think I ended up with that code because it was not explicitly reset in the original code. That was arguably correct because
flexdll_relocate
is called from two places (if I didn't miss any other):flexdll_dlopen
wherecode
has already been reset,flexdll_init
wherecode
has been set to its initial value 0.This made me realize that I had forgotten to initialize the values when they are malloc-ed!
So I’ve rewritten the code so that:
TLS_ERROR_RESET
, bothcode
andlast_error
are reset (so no_LAST
),code
near the call toget_tls_error(TLS_ERROR_RESET)
are removed,malloc
, just to make sure; the structure should be malloc-ed on a call to one of the initialisation entrypoints, in which case it will be initialised again just a few lines later, but that will ensure that a buggy program callingdlerror
without a previous call todlopen
will get a reliable reasonable behaviour.