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

Segfault when cleaning metadata cache [CORE4869] #5165

Closed
firebird-automations opened this issue Jul 9, 2015 · 4 comments
Closed

Segfault when cleaning metadata cache [CORE4869] #5165

firebird-automations opened this issue Jul 9, 2015 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

An issue (as core dump) is initially reported by IbPhoenix.

Under some circumstances it may happen that prc_existence_lock is NULL when cleaning metadata cache.
For example when obsolete procedure is scanned again in MET_procedure() any error raised out of parse_procedure_blr() function will cause catch() block in the end of function release and nullify prc_existence_lock, keeping old prc_request present and setting no obsolete flag again.
This makes necessary check for lock's presence when cleanin cache.

Commits: fb326c8 9474a22 FirebirdSQL/fbt-repository@60665a3 FirebirdSQL/fbt-repository@d1aa662

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 2.5.5 [ 10670 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Not enough information

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