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
ISQL - "Segmentation fault (core dumped)" after CREATE DATABASE [CORE5362] #5635
Comments
Commented by: @AlexPeshkoff What I use is definitely not KUbuntu but... I can not reproduce an issue: bash-2.05b# ./isql Take into an account that _such_ bugs are typically caught by our regression tests. Please provide stack traces for all threads - may be this helps. |
Modified by: Gabor Boros (gaborboros)environment: Kubuntu 14.04.5 64bit, Firebird 3.0.1 installed from Firebird-3.0.1.32609-0.i686.tar.gz. => Kubuntu 14.04.5 64bit, Firebird 3.0.1 installed from Firebird-3.0.1.32609-0.amd64.tar.gz |
Commented by: Gabor Boros (gaborboros) I use amd64 build for 64bit certainly, i686 is just a mistype, corrected it. How can I create a stack trace? |
Commented by: @AlexPeshkoff As far as I can see you already have core dump: Install appropriate debuginfo file - just untar it in the "/" of your FS. Now you may use gdb to analyze coredump: |
Commented by: Gabor Boros (gaborboros) I hope this is what you want: [New LWP 6375] Thread 3 (Thread 0x7f0db20207c0 (LWP 6368)): Thread 2 (Thread 0x7f0daff13700 (LWP 6369)): Thread 1 (Thread 0x7f0da9ff5700 (LWP 6375)): |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Gabor Boros (gaborboros)
Steps to reproduce:
root@kubuntu:/opt/firebird/bin# ./isql -user SYSDBA employee
Database: employee, User: SYSDBA
SQL> CREATE USER MYADMIN PASSWORD '123' GRANT ADMIN ROLE;
SQL> QUIT;
root@kubuntu:/opt/firebird/bin# ./isql -user MYADMIN employee
Database: employee, User: MYADMIN
SQL> CREATE DATABASE '/home/DB/MYDB.FDB' PAGE_SIZE 4096;
Commit current transaction (y/n)?y
Committing.
SQL> QUIT;
Segmentation fault (core dumped)
root@kubuntu:/opt/firebird/bin#
The text was updated successfully, but these errors were encountered: