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

serious array bug crashes server [CORE406] #750

Closed
firebird-automations opened this issue Dec 29, 2002 · 2 comments
Closed

serious array bug crashes server [CORE406] #750

firebird-automations opened this issue Dec 29, 2002 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: woodsplitter (woodsplitter)

SFID: 659610#⁠
Submitted By: woodsplitter

I've encountered a serious array-related bug in
Firebird, which is easily replicable on versions 1.0,
1.0.2, and the latest 1.5 alpha (1.5.0.1761 Firebird
1.5 Alpha 5). The consequences of the bug differ
between 1.0.x and 1.5.

I'm writing a unit test for the array support that I
just added to kinterbasdb (a Python driver for
Firebird). My test code is designed to test arrays of
every data type that can be stored as an array element,
and to test every possible number of dimensions for
each data type (1 to 16, according to the
documentation), with random sizes for each dimension.
Upon running a preliminary version of this unit test, I
noticed that the following statement crashes the
Firebird server process:
-------
create table "tbl_271" (col
SMALLINT[461,274,583,252,375,170,772,143,153,172,722])
-------
The dimension sizes in that statement are just the
random sizes generated by my test code; the simpler
statement below has the same effect:
-------
create table blah (col smallint[2,2,2,2,2,2,2,2,2,2,2]);
-------
The key is the number of dimensions: a 'create table'
statement that specifies more than 10 dimensions
crashes the server (Firebird 1.0.x), or is accepted but
not applied (that is, the table is not created) on
(Firebird 1.5a5). Also, I have not observed that the
data type of the array elements has any
effect--SMALLINT, INTEGER, CHAR, FLOAT, and TIMESTAMP
all behave the same way, at least.

This crash has nothing to do with the client library
that I'm writing; it's a server problem, and is
replicable with isql and IBOConsole.

Here are the specifics of my system configurations:
1. Windows 2000 SP3 / Firebird SuperServer 1.0.2
2. Windows NT 4 SP6a / Firebird SuperServer 1.5.0.1761
Firebird 1.5 Alpha 5 (I also observed the bug earlier
on this machine with Firebird 1.0.)

Thanks.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10430 ] => Firebird [ 14724 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

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