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

disconnect [CORE1010] #1420

Closed
firebird-automations opened this issue Nov 22, 2006 · 15 comments
Closed

disconnect [CORE1010] #1420

firebird-automations opened this issue Nov 22, 2006 · 15 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Arteev Alexei (arteev.a)

Is related to QA24

CREATE EXCEPTION RDB$TEST 'Test';
commit;
set term ^ ;
CREATE OR ALTER TRIGGER RDB$PROCEDURES_BIU FOR RDB$PROCEDURES
ACTIVE AFTER UPDATE OR DELETE POSITION 0
as
begin
-- if (...) then
EXCEPTION RDB$TEST;
end^

commit^

create or alter procedure proctest
returns (result integer)
as
begin
result = 0;
suspend;
end
^

set term ; ^

commit;
exit;

FB 1.5:
This operation is not defined for system tables.
unsuccessful metadata update.
MODIFY RDB$PROCEDURES failed.
exception 4.
Test.

FB 2.0: Disconect

Commits: 4d45414 4e9130d

====== Test Details ======

Removed old code: all attempts to create triggers on SYSTEM tables now are prohibited, even for SYSDBA -- see CORE4731

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

We have a local buffer overrun in DYN_error(), while copying tdbb_status_vector to local_status. It seems to be the first time (DYN errors + stack trace facility) when 20 status words are not enough to store the complete error info. And the code that performs a vector truncation doesn't look safe to me.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Claudio Valderrama C. [ robocop ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

priority: Major [ 3 ] => Critical [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Fix Version: 2.0.1 [ 10090 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Claudio Valderrama C. [ robocop ] => Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

resolution: Fixed [ 1 ]

Fix Version: 2.1 [ 10041 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

Fix verified, test added.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

Reopened to update ticket information.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

resolution: Fixed [ 1 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Fix Version: 2.1 Alpha 1 [ 10150 ]

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue is related to QA24 [ QA24 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11342 ] => Firebird [ 15339 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Done successfully

Test Details: Removed old code: all attempts to create triggers on SYSTEM tables now are prohibited, even for SYSDBA -- see CORE4731

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