Re: [Gm2] Fedora Core 14 compatibility

[SiTex Graphics]

Hi Gaius,

Thanks for looking into this.  I sent the user a build linked with
FIO.o -O0, and he reports getting the same error.

Here's the call stack from gdb:

#0  0x00007ffff6ca32d5 in raise () from /lib64/libc.so.6
#1  0x00007ffff6ca4beb in abort () from /lib64/libc.so.6
#2  0x000000000063cfb2 in M2RTS_HALT (exitcode=-1) at
../../gcc-4.1.2+gm2-cvs-latest
/gcc/gm2/gm2-libs-iso/M2RTS.mod:145
#3  0x00000000006509cc in RTExceptions_DefaultErrorCatch ()
   at ../../gcc-4.1.2+gm2-cvs-latest/gcc/gm2/gm2-libs/RTExceptions.mod:153
#4  0x0000000000403c09 in init(int, char**) ()
#5  0x0000000000403f79 in main ()

Am I right that init() calls the initialization code for each module?
If so, is there a build option to have the executable print a message
as each module is initialized?  Any other suggestions for how to track
down the offending module (which may well be one of ours)?

Thanks,
Scott



On Wed, Oct 19, 2011 at 5:32 AM, Gaius Mulley <address@hidden> wrote:
> SiTex Graphics <address@hidden> writes:
>
>> On Tue, Oct 11, 2011 at 2:50 AM, Gaius Mulley <address@hidden> wrote:
>>> is this a 32 bit or 64 bit version of FC 14?  I've not run either - but
>>> I'll download/install and try and reproduce the bug,
>>
>> 64-bit
>>
>> Thanks for taking a look.
>
> Hi Scott,
>
> I've reproduced the bug and indeed it crashes before the main
> application starts - if you link against the -O2 libraries.  There is a
> bug in the compilation of FIO.mod when -O2 is used.  As a work around it
> should be possibly to copy
>
>  build-4.1.2/gcc/gm2/gm2-libs/FIO.o
>
> into your user area where the link is performed.  Thus linking against
> the -O0 FIO.mod and -O2 other libraries.  I'm still looking into the
> actual bug (for the correct fix),
>
> regards,
> Gaius
>