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

IB crashes with two procedures intermixed. [CORE489] #839

Closed
firebird-automations opened this issue Nov 27, 2000 · 3 comments
Closed

IB crashes with two procedures intermixed. [CORE489] #839

firebird-automations opened this issue Nov 27, 2000 · 3 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Claudio Valderrama C. (robocop)

SFID: 223514#⁠
Submitted By: robocop

-----Original Message-----
From: DJK GreenSystems
Sent: Jueves 26 de Octubre de 2000 3:12
To: Claudio Valderrama C.
Subject: Re: Metadata

You should do the following:

These two procedures expect an order and an order-line number. The following will make IB crash:
// Show al possible parties on stock, with the same characteristics
select * from GET_ORDVRD(258,1)
// Show the status of the stock (matched, alternatives etc)
select * from INKORDVRDSTATUS(258,1)
// First one
select * from GET_ORDVRD(258,1)

I did have more problems. This is the most easy one to regenerate, because it can be done only with Interbase. Making changes to one of the procedures will lead that the system does not crash, but that it happened on other places.
[snip]
I would be very glad if this problem will be solved. We have a number of small customers, we want to work with Interbase. Please keep in touch.

Regards,
Dirk-Jan van der Kooij
-----End of Original Message-----

Now, what happens after the sequence of procedures is executed is simply that IB crashes due to a memory problem. Such sequence (see above) is shown again here:
select * from GET_ORDVRD(258,1);
select * from INKORDVRDSTATUS(258,1);
select * from GET_ORDVRD(258,1);

Example database will be available at
http://www.cvalde.com/bugs/gstest3.zip
Please try it as confidential. The person that sent me it several months ago gave me permission to share it but he doesn't want to show his business logic to all the world, of course. I had to post the backup because the error can't be reproduced by simply preparing the execution of procedures; they have to be run with minimal data.

C.

@firebird-automations
Copy link
Collaborator Author

Commented by: Alice F. Bird (firebirds)

Date: 2003-01-23 10:23
Sender: dimitr
Logged In: YES
user_id=61270

I'm able to reproduce it in v1.0, but v1.5 doesn't have this bug, so I've
marked it as fixed.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10513 ] => Firebird [ 14821 ]

@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

1 participant