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

"fb_lock_print -c" hangs server [CORE3454] #3815

Closed
firebird-automations opened this issue Apr 28, 2011 · 5 comments
Closed

"fb_lock_print -c" hangs server [CORE3454] #3815

firebird-automations opened this issue Apr 28, 2011 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

Lock print remaps robust shared mutex betwen different memory locations. This probably violates posix rules that say "mutex, returned by pthread_mutex_init, can't be copied to another location", though not explicitly. On attempt to unlock such remapped mutex linux returns no error, but does not release mutex.

Commits: ca42e73

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

FB3 does not require fixing - remapping was fixed during general code cleanup

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5.1 [ 10333 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants