mf-runtime.c IC error..
Seema S. Ravandale
ravandale@cse.iitb.ac.in
Mon Jun 11 11:03:00 GMT 2007
Hi.
Thanks for the help. The problem is solved anyways.
After few trials, i came to know that few memory locations were getting
overwritten by mallacious data and thats bcoz of ggc_realloc. In my prog
ggc_realloc was getting called many times. When i increased the size for
the very first allocation so that there will be fewer calls to
ggc_realloc, "Make" went through.
Is there any known/similar problem related to ggc_realloc() ?? Is it to do
with book-keeping information getting merged with allocated memory or it
is taken care by gcc-garbage collector??
Thank you.
- Seema
> hi seema,
> Did you try checking the backtrace when you get the segfault.
> Except for a corrupted value of __mf_opts, there is not much there that
> can cause a segfault. Try putting a bpt on fancy_abort and backtrace
> when it is hit.
>
> HTH
> saurabh
>
> On Mon, 2007-06-11 at 14:34 +0530, Seema S. Ravandale wrote:
>> Hi...
>> I have inserted some code for available analysis in the source code of
>> GCC4.0.2
>> But "make" fails at the file mf-runtime.c
>> the error i got is as follow:
>>
>
>
More information about the Gcc
mailing list