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

Server crashes when attempting to trace activity on database having a db-level trigger [CORE4225] #4549

Closed
firebird-automations opened this issue Sep 18, 2013 · 9 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pavel-zotov

Attachments:
gdb-firebird.130918_170533.2.zip

The following db-level trigger fires each time when I connect to .fdb and FB craches if trace session is active in that moment.

SQL> set blob all;
SQL> show trigger trg_connect;
There is no trigger TRG_CONNECT in this database
SQL> show trigger trg_logon;
TRG_LOGON, Sequence: 0, Type: ON CONNECT, Active
as
begin
if ( current_user = 'CALIBRATOR' )
then
execute procedure SYS_CONNECT_CALIBRATE;
end
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

SQL> show version;
ISQL Version: WI-V2.5.3.26682 Firebird 2.5
Server version:
Firebird/linux AMD64 (access method), version "LI-T3.0.0.30653 Firebird 3.0 Alpha 1"
Firebird/linux AMD64 (remote server), version "LI-T3.0.0.30653 Firebird 3.0 Alpha 1/tcp (vmoel63.loc
al)/P12"
Firebird/x86/Windows NT (remote interface), version "WI-V2.5.3.26682 Firebird 2.5/tcp (CSMIRROR)/P12
"
on disk structure version 12.0

Please see attch with result of stack trace for coredump.

PS. There is *no* such effect in FB 2.5.x (neither in current nor in old versions of ~octomeb...-december 2012).

Commits: 8c3c0ba b9f34c1 fc1d01f FirebirdSQL/fbt-repository@b2d92bb FirebirdSQL/fbt-repository@542a3f1 FirebirdSQL/fbt-repository@27863ae

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

Test not needed: WI-T3.0.0.30566 Firebird 3.0 Alpha 1 crashed even from single trace session start by FBSVCMGR (w/o connection to database), with trivial config like:
database =
{
enabled = true
}

Such faults should now be catched by many other tests where FBSVCMGR is called as subprocess.

@firebird-automations
Copy link
Collaborator Author

Commented by: @pavel-zotov

stack trace for coredump

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

Attachment: gdb-firebird.130918_170533.2.zip [ 12373 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Component: Engine [ 10000 ]

summary: FB-3 craches with coredump when attempting to trace activity on database that have db-level trigger => Server crashes when attempting to trace activity on database having a db-level trigger

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

While v2.5 is not affected it is better to have this patch applied there too.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

Fix Version: 2.5.3 [ 10461 ]

Fix Version: 3.0 Alpha 2 [ 10560 ]

@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

Test Details: Test not needed: WI-T3.0.0.30566 Firebird 3.0 Alpha 1 crashed even from single trace session start by FBSVCMGR (w/o connection to database), with trivial config like:
database =
{
enabled = true
}

Such faults should now be catched by many other tests where FBSVCMGR is called as subprocess.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Covered by another test(s)

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