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

Access violation with text value of parameter LockMemSize [CORE5859] #6119

Open
firebird-automations opened this issue Jun 25, 2018 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Maxim Kuzmin (cybermax)

We using FB 2.5.7 x32. When I in firebird.conf changing value of parameter LockMemSize from default value 1048576 to "2M" or other, I can't connect to server - when using fbembed.dll, get access violation in dll, when try connect to server - "Error writing data to the connection.". In FB 3.0 using "2M" work without problem.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Literal suffixes K/M/G were introduced in FB3, they are not expected to work in FB 2.5. That said, the server surely shouldn't crash.

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

With 2 bytes of shared lock memory? Which is less than header size? I'd say crash is almost expected behavior :) Certainly we can add some protection but if we decide to do it protection code should be applied systematically to all .conf files, not only single value.

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

Based on the comments, it seems this case is "Won't Fix" -- support for K/M/G was only added to v3.x, "protection code" logic for .conf file values is a separate feature request (though related to this issue)

@firebird-automations
Copy link
Collaborator Author

Commented by: Maxim Kuzmin (cybermax)

Sean Leyne, I agree with "Won't Fix". Can you create a ticket for implementation protection logic? It will be a little difficult for me to describe it.

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

1 participant