Bug 240314

Summary: prelink infinitely loops when processing /usr/bin/fparser
Product: [Fedora] Fedora Reporter: Eric Harney <eharney>
Component: prelinkAssignee: Jakub Jelinek <jakub>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-06-04 00:11:22 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:
Attachments:
Description Flags
gdb backtrace during infinite loop none

Description Eric Harney 2007-05-16 13:32:59 UTC 
Description of problem:
prelink goes into an infinite loop when processing /usr/bin/fparser (part of frysk)

Version-Release number of selected component (if applicable):
prelink-0.3.10-1
frysk-0.0.1.2007.03.13.rh1-1.fc7
md5sum 1998f58450b20f2b8f4d37a59b8aacca  /usr/bin/fparser

How reproducible:
Every time

Steps to Reproduce:
1. prelink /usr/bin/fparser
  
Actual results:
Hangs in infinite loop

Additional info:
See attached backtrace, gathered by attaching gdb to prelink, ctrl-c, and "bt full"
Comment 1 Eric Harney 2007-05-16 13:32:59 UTC 
Created attachment 154820 [details]
gdb backtrace during infinite loop
Comment 2 Eric Harney 2007-05-16 15:08:55 UTC 
Also, running "prelink -y" on _any_ of the /usr/bin/f* from the frysk package
will either hang as this first one did, or print loads of gibberish to the
screen.  This is a nasty one.
Comment 3 Jakub Jelinek 2007-05-25 13:10:48 UTC 
Can't reproduce, with the same i386 prelink package and same frysk package, same
md5 sum before prelinking.
Comment 4 Eric Harney 2007-05-25 16:43:26 UTC 
I can no longer reproduce the first problem either, but am still encountering
the second one... running "prelink -y /usr/bin/fparser" sits for a while and
then prints a load of random data to the screen.  This happens both before and
after the original file has been prelinked.
Comment 5 Eric Harney 2007-06-04 00:11:22 UTC 
Can't reproduce the main issue I was reporting any more, and the second
complaint was my error.  I think this one can be closed.