Bug 1134339
| Summary: | Error in pdo_odbc | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Patrick Monnerat <patrick> | ||||||
| Component: | php | Assignee: | Remi Collet <fedora> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 23 | CC: | fedora, jorton | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-12-20 12:51:06 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 931391 [details]
Patch for version 5.5.15
Such bug have to be fix upstream first. Can you open a upstream bug report, with your patch proposal ? I would have done it already if the code in the master git repository was not yet fixed :-) I think they are already aware of it, but this has not yet reached F20 (not backported to 5.5.15). Are you sure I should do it? It's just a backport. Yes please do it. master is now terribly different from 5.5/5.6 (because of phpng + int64 merge). I can find any trace of any bug fix on this file. Sems related to https://github.com/php/php-src/commit/8210b3b8c470ec91bee89bad4d34c482aab13406 Which is a "support for phpng" generix commit. Yes, it seems it has been fixed by this commit, as a part of a larger action (processing references, API change, etc). In any case, the erealloc() call at line 497 is not here anymore and the code reorganization in the switch case should resolve the problem. Well, the change is only 15 days old and the bug is not explicitly reported. Thus I left a report: https://bugs.php.net/bug.php?id=67919 Thanks for locating the commit. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. F20 --> rawhide. Still not fixed in 5.6.9. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 931390 [details] Program causing the bug Description of problem: When using a bound in/out parameter preset with a string constant, prepared statement execution fatally fails with message "zend_mm_heap corrupted". Version-Release number of selected component (if applicable): php-5.5.15-1 How reproducible: Always Steps to Reproduce: 1. Adjust the attached pdobug.php program to your test database. 2. Run it. Actual results: zend_mm_head corrupted Expected results: Display of sql execution result and normal end of program Additional info: The crash occurs because the pdo_odbc code tries to erealloc the constant. If the pdobug.php program is modified to preset the parameter value with an expression, the bug does not occur. This bug seems to have been fixed upstream. However the fix is not compatible with version 5.5.15. Please find a patch for 5.5.15 in attachment.