Bug 22235 - egcs produces bad .o some time
Summary: egcs produces bad .o some time
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: egcs   
(Show other bugs)
Version: 6.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-12-13 16:23 UTC by Need Real Name
Modified: 2005-10-31 22:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-02 19:16:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2000-12-13 16:23:18 UTC
I moved from redhat 5.2 to 6.0 and found that I get following error

gcc -DLINUX_RH -D_POSIX_SOURCE -I. -I../linux -I../generic
-I../../../header/linux_rh_60 -I../../../header/linux
-I../../../header/generic -I../../../../../share/linux_rh_60/tps/header
../generic/error.c -o error.o
ar cq libcscomm.a authorize_client_rpc.o connect_to_rpc_service_rpc.o
login_rpc.o utils_rpc.o get_handle_rpc.o bind_tcp_port_rpc.o
get_tcp_ports_rpc.o register_interface_rpc.o clnt_async.o svc_async.o
csc_socket.o char_descriptor.o error.o csc_platform_utils.o
BFD: error.o: invalid string offset 6912 >= 99 for section `.shstrtab'
BFD: error.o: invalid string offset 8448 >= 99 for section `.shstrtab'
BFD: error.o: invalid string offset 11008 >= 99 for section `.shstrtab'
gcc -o epcommd procedure.o server.o epcommd.o getmount.o parsemnt.o
esl_directory.o direntries.o epcplatform.o rpcsvc.o cluster.o -L.
-L../../../../../../share/linux_rh_60/esl/lib -L.
-L../../../../csc/fbrowser -Bstatic -lepcomm_api -lepcomm_svc -lcscomm
-lcsc_config_clnt -lcsc_common_clnt -llogging -lesl_utils_c -leerrno
collect2: ld terminated with signal 11 [Segmentation fault], core dumped
/usr/bin/ld: error.o: invalid string offset 6912 >= 99 for section
/usr/bin/ld: error.o: invalid string offset 8448 >= 99 for section
/usr/bin/ld: error.o: invalid string offset 11008 >= 99 for section

The same code if compiled on redhat 5.2 will work fine without any problem.
On 6.0 I first loaded egcs-1.1.2-12 & egcs-c++-1.1.2-12. On seeing the
above problem I then moved to egcs-1.1.2-30 & egcs-c++-1.1.2-30. But this
also did not fix the problem.

On a side note very few times the compilation does go fine without any
problem.  It seems to me that most of the time error.o object in not
generated correctly. I did cmp -l on bad error.o and good error.o and found
that at that difference is of one additional byte. See below:

jain1 66> cmp -l linux_rh_60.bad/error.o linux_rh_60.good/error.o
  7845   0  33
  7846  33   0
  7849   0   1
  7850   1   0
  7853   0   6
  7854   6   0
  7861   0 100
  7862 100   0
  7865   0 262
  7866 262   6
  7867   6   0
  7877   0  20

Please help as I cannot proceed further. Thanks....

Comment 1 Jakub Jelinek 2000-12-15 16:48:52 UTC
This definitely is not compiler issue (error.o is created by assembler),
but it looks like either hardware problem (most probably) or some kernel
corruption issue. I'd suggest you try it on some other hardware or try
some newer kernel (such as from 6.2 distribution).

Comment 2 Need Real Name 2000-12-20 14:23:59 UTC
I have the same machine running 5.2 and 6.0. On 5.2 it compiles perfect. Hence
it cannot be a hardware problem.  As far as your suggestion to put 6.2 kernel on
6.0 operating system, I am not sure whether it is really desirable for following

1. I want to create my application on 6.0 only so that I can support it for
6.0/6.1/6.2/7.0. I am not sure that after putting 6.2 kernel I would be able to
support 6.0 and 6.1.
2. I see another bug# 5853 reported the similar problem.
3. I installed the 6.0 kernel out of the CDROM provided by redhat. I am sure
that this kernel is not buggy.

Let me know your thoughts. Please give your highest priority to resolve this

Comment 3 Need Real Name 2001-01-17 21:18:45 UTC
I tried on another machine but it gives me the same problem. Please help!!

Comment 4 Jakub Jelinek 2004-10-02 19:16:52 UTC
If you are still able to reproduce this with some current distribution
(FC2 or FC3t2), please reopen.

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