| Ticket UUID: | 3192580 | |||
| Title: | invalid pointer freed | |||
| Type: | Bug | Version: | obsolete: 8.5.7 | |
| Submitter: | mzalokar | Created on: | 2011-02-25 19:58:16 | |
| Subsystem: | 41. Memory Allocation | Assigned To: | hobbs | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2011-03-12 04:20:04 | |
| Resolution: | None | Closed By: | sf-robot | |
| Closed on: | 2011-03-11 21:20:04 | |||
| Description: |
The program runs for a while, then this. This is using the standard python, tkinter, tk and tcl included in RHEL 6. # rpm -qa | egrep "^tcl-|^tk-|^tkinter-|^python-" python-pycurl-7.19.0-5.el6.x86_64 tcl-devel-8.5.7-6.el6.x86_64 python-libs-2.6.5-3.el6.x86_64 python-ldap-2.3.10-1.el6.x86_64 python-slip-0.2.11-1.el6.noarch python-iniparse-0.3.1-2.1.el6.noarch tk-devel-8.5.7-5.el6.x86_64 python-2.6.5-3.el6.x86_64 python-urlgrabber-3.9.1-7.el6.noarch python-devel-2.6.5-3.el6.x86_64 tkinter-2.6.5-3.el6.x86_64 tcl-8.5.7-6.el6.x86_64 python-ethtool-0.3-5.1.el6.x86_64 python-iwlib-0.1-1.2.el6.x86_64 python-setuptools-0.6.10-3.el6.noarch tk-8.5.7-5.el6.x86_64 python-meh-0.9-1.el6.noarch | |||
| User Comments: |
sf-robot added on 2011-03-12 04:20:04:
allow_comments - 1 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). dkf added on 2011-02-26 04:20:00: Impossible to tell what's wrong on the evidence provided. It could be python code trying to free an object from the wrong thread (Tcl_Obj values are strongly thread-bound) or passing in an invalid value. It could also be a bug in code which has subsequently returned (having put the world into an inconsistent state first). Memory deallocation faults have a tendency to not be closely correlated in the code with the bug as memory management is a complex process-global resource. A minimal program that reproduces the fault would be superbly useful in progressing this (better yet, purify/valgrind run)... (It's even possible that it is a fault in your own code; I see that you have modules compiled into your home directory loaded. It's just not possible to rule them out for now.) mzalokar added on 2011-02-26 02:58:16: File Added - 402723: entv_RHEL6_crash | |||
Attachments:
- entv_RHEL6_crash [download] added by mzalokar on 2011-02-26 02:58:16. [details]