Bug 144142
Summary: | double free or corruption (!prev) in Gnome application | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Erich Schroeder <erich> |
Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-01 01:25:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Erich Schroeder
2005-01-04 20:35:44 UTC
This sounds like an application problem and is actually unrelated to xorg. Basically glibc is warning you about a dangerous bug *in gphpedit*. The reason the message appears is because gphpedit is faulty and turning off the warning by doing MALLOC_CHECK_=0 is only allowing silent memory corruption to happen. This could be disasterous (imagine an unseen line of the PHP you are editing having a "<" change to ">"). Reporting the bug to the gphpedit authors is pretty much the best thing you could have done short of pulling out gdb/valgrind and fixing the source of gphpedit yourself. Since gphpedit is not a part of Fedora there is nothing more the devs can do on this end. I suspect all the other double free warning bugs are against packages actually shipped with base Fedora... I imagine this is correct, although I posted it here because I see the problem in FC3 but not FC2. Anyway, sorry if it is wasting time. eks Sitsofe is correct, this is not an xorg-x11 bug, nor a Fedora Core bug. It is a bug in the application you are using. The reason the problem shows up in Fedora Core 3, is because FC3 glibc has new security features designed to detect security flaws in applications and report warnings when an application has a security vulnerability. This feature was not present in Fedora Core 2, so running this insecure application in FC2 will not give you any security warnings, however in both cases the software is insecure. The problem should be reported directly to the authors of the insecure application, so they can fix it. Setting status to NOTABUG, because this is not an xorg-x11 or Fedora Core bug. |