Bug 138770 - pinfo corrupts memory --> glibc kills it
Summary: pinfo corrupts memory --> glibc kills it
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pinfo
Version: 3
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-11 01:33 UTC by Sami Farin
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-12-23 18:13:31 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
memory corruption fix (436 bytes, patch)
2004-11-11 01:35 UTC, Sami Farin 		no flags Details | Diff
small memleak fix (310 bytes, patch)
2004-11-11 01:36 UTC, Sami Farin 		no flags Details | Diff
View All

Description Sami Farin 2004-11-11 01:33:22 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041020

Description of problem:
pinfo corrupts glibc's internal states, causing abnormal program
termination if you're unlucky.

also, fixed one small memory leak (patch attached).


Version-Release number of selected component (if applicable):
pinfo-0.6.8-2

How reproducible:
Always

Steps to Reproduce:
1. have gcc-3.4.3 info files installed.  (maybe other versions work, too.)
2. start "pinfo gcc"
3. select ``Keyword Index''
4. select any of the topics.

    

Actual Results:  *** glibc detected *** double free or corruption:
0x0807aec8 ***

(pinfo gets killed)

Expected Results:  getting the topic I wanted.


Additional info:

glibc-2.3.3-73 (i686)
Comment 1 Sami Farin 2004-11-11 01:35:17 UTC 
Created attachment 106466 [details]
memory corruption fix
Comment 2 Sami Farin 2004-11-11 01:36:48 UTC 
Created attachment 106467 [details]
small memleak fix
Comment 4 Mike A. Harris 2004-12-23 18:13:31 UTC 
Thanks for the report, and patches!  Patches applied to 
pinfo-0.6.8-8, and built in Fedora development.

Thanks again.
Note You need to log in before you can comment on or make changes to this bug.