Re: STORAGE_ERROR in adainit

[James Alan Farrell <anonymous@anonymous.com>]

On Tue, 17 Aug 2004 21:37:11 GMT, Bj�rn Persson
<spam-away@nowhere.nil> wrote:


>Yes, I get the same error messages when the main program is in C:
>
>
>file clash_test_2_ada.ads:
>
>package Clash_Test_2_Ada is
>end Clash_Test_2_Ada;
>
>
>file clash_test_2_c.c:
>
>void program_error() {}
>
>int main(int argc, char** argv) {
>    adainit();
>    program_error();
>    adafinal();
>    return 0;
>}
>
>
>$ gcc -c clash_test_2_c.c
>$ gnatmake clash_test_2_ada
>gcc -c clash_test_2_ada.ads
>$ gnatbind -n clash_test_2_ada.ali
>$ LANG=en_US gnatlink clash_test_2_ada.ali clash_test_2_c.o
>/home/bjorn/ada/gcc-3.4.0-inst/lib/gcc/i686-pc-linux-gnu/3.4.0/adalib/libgnat.a(s-stalib.o)(.data+0x78):/home/bjorn/ada/gcc-3.4.0-objdir/gcc/ada/rts/s-stalib.adb:104: 
>multiple definition of `program_error'
>clash_test_2_c.o(.text+0x0): first defined here
>/usr/bin/ld: Warning: size of symbol `program_error' changed from 5 in 
>clash_test_2_c.o to 24 in 
>/home/bjorn/ada/gcc-3.4.0-inst/lib/gcc/i686-pc-linux-gnu/3.4.0/adalib/libgnat.a(s-stalib.o)
>/usr/bin/ld: Warning: type of symbol `program_error' changed from 2 to 1 
>in 
>/home/bjorn/ada/gcc-3.4.0-inst/lib/gcc/i686-pc-linux-gnu/3.4.0/adalib/libgnat.a(s-stalib.o)
>collect2: ld returned 1 exit status
>gnatlink: cannot call /home/bjorn/ada/gcc-3.4.0-inst/bin/gcc
>
>

I'll play around with this when I get a chance.


>> I found the problem by creating a small test program.  When I did that
>> I got a linker warning pointing to program_error (indicating in fact
>> that it is used as data in one place and as a function in another
>> place).
>
>So the difference is that you get a warning but an executable is 
>produced, while for me, Gnatlink treats the clash as a fatal error and 
>refuses to produce an executable.
>

Perhaps you have a newer version of gnatlink?  It seems to me we've
upgraded a month or so ago, but perhaps that upgrade was only some
libraries (we're using asis, and we may have only upgraded the asis
libs instead of the compiler).

Other than that I don't understand why you would have different
results.  Perhaps it is because my program_error C function is in a
library, not in a .o file?  Don't know what different that would make,
though.  I'll play around with the above program to see what I get.

>> In the production program I am getting an unrelated linker warning,
>> but I think for some reason that warning was preventing the warning
>> that I needed from being displayed.
>
>While I don't know what that warning is about, I'd recommend that you 
>fix it. It may well be another fatal error.

*sigh* in a perfect world...

Thanks again,
James Alan Farrell