[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gm2] Fedora Core 14 compatibility

From: Gaius Mulley
Subject: Re: [Gm2] Fedora Core 14 compatibility
Date: Fri, 21 Oct 2011 00:05:36 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

SiTex Graphics <address@hidden> writes:

> 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/
> #1  0x00007ffff6ca4beb in abort () from /lib64/
> #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

Hi Scott,

at present there is no build option to print out a message - it could be
done if required.  I tend to run the executable under gdb, break at main
and single step into each init function - this is much harder if it is
built as a shared library though.  But for a regular 'a.out' it works
well - especially if one uses 'fin' to finish each init function.
Let me know if the change to the build option to insert 'printf's would
be a useful debugging feature,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]