Issue 244

Summary: Linux binary for 613 fails to install properly
Product: Installation Reporter: issues@www <issues>
Component: codeAssignee: dirk.voelzke
Status: CLOSED IRREPRODUCIBLE QA Contact: issues@installation <issues>
Severity: Trivial    
Priority: P1 (highest) CC: issues
Version: 613   
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on: 231, 234, 235, 236, 241    
Issue Blocks:    

Description issues@www 2000-12-17 01:08:22 UTC 
The setup script for 613 fails to complete: 
A 20561920 byte core is dumped and gdb reports that: 

Core was generated by `/tmp/sv001.tmp/setup.bin'.
Program terminated with signal 11, Segmentation fault.
#0  0x40fba691 in ?? ()

The setup doe not allow for a proper deinstallation either, 
since the file setup.ini is not written in the prgram subdirectory
(it looks that this is the step where the core is dumped). 

I am running a Redhat-7.0/Mandrake-7.2 hybrid Linux, kernel 2.2.18 (or
2.4.0-test12) with glibc-2.2. Is it conceivable that your setup.bin sis not
compatible with glibc-2.2, causing the core dump? 


The bug occurs whether I run setup as soot or as myself. 

BTW -- naming the script "setup" just to make it look like Windows was 
an error: Redhat Linux has its own "setup" command.
Comment 1 issues@www 2000-12-17 01:16:41 UTC 
Issues 231, 234, 235, 236, 241 all report the same behavior. 
Some of the reporters may not have noticed the core dump by setup.bin 
or the lacking setup.ini file.
Comment 2 issues@www 2000-12-17 01:30:23 UTC 
Issues 231, 234, 235, 236, 241 all report the same behavior. 
Some of the reporters may not have noticed the core dump by setup.bin 
or the lacking setup.ini file.
Comment 3 Unknown 2001-02-27 10:35:11 UTC 
Thanks.
Comment 4 Unknown 2001-11-08 22:44:46 UTC 
changing QA contact from bugs@ to issues@
Comment 5 Unknown 2002-01-21 13:12:44 UTC 
for you...
Comment 6 dirk.voelzke 2002-01-21 13:18:58 UTC 
Ok, I've tested version 641 C instead of 613 using Redhat 7.2 instead 
of Redhat 7.0, but now everything works for me
Comment 7 lohmaier 2002-03-14 00:19:20 UTC 
everything works, so this one can be closed