csect declaration, and this is presumably what the linker is complaining about. If we do some grepping, something interesting comes out: The section that it references must be declared by a. bs is a C_BSTAT declaration, which indicates the section in which the following variable resides. (my_init is a static variable initialized with a value my_uninit is uninitialized.) Here is an excerpt from the assembly produced by the minimal test case:
The problem is triggered when debugging information is generated for a variable declared as "static" (whether inside or outside a function). Note that it was written on a 64-bit AIX system, hence the use of -mai圆4, but the bug also seems to occur in 32-bit mode. The minimal test case has a target which triggers the bug (try-1), a target which does not (try-2), a target to compile to assembly, and a "clean" target. Attached is a tarball containing a minimal test case. I've dug into this, and believe I have found what's going on.
The new symbol cannot be associated with a csect and The symbol refers to a csect with symbol number 0, which was notįound. Ld: 0711-593 SEVERE ERROR: Symbol C_BSTAT (entry 12) in object foo.o:
The system had not been kept up-to-date with IBM system patches, however one day we found these to be needed (to allow a 64-bit Java install), and so installed about three years' worth of updates over the course of a few days.Īfter the first couple of updates, we noticed that debug-enabled builds of our C software began to fail with this error message: GCC 4.5.1 has worked fine on this AIX 5.3 system for some time.
0 kommentar(er)
