tags 347697 + moreinfo
thanks
please recheck with gcc-4.1 (from unstable)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Falk Hueffner wrote:
> I just briefly tried to debug it, but apparently, it even wants a
> Yahoo password or something. This is more effort than I want to spend
> on something that I suspect isn't even a gcc bug (and frankly, I
> wouldn't expect anybody else to jump in).
Have you read the message
Chris Howie <[EMAIL PROTECTED]> writes:
> Falk Hueffner wrote:
>> the fact that your program crashes in glibc memory manangement makes
>> it quite unlikely that this is a compiler bug. Can you try valgrind?
>> Also, your test case is quite large, would it be possible to get
>> something smaller?
>
Falk Hueffner wrote:
> the fact that your program crashes in glibc memory manangement makes
> it quite unlikely that this is a compiler bug. Can you try valgrind?
I can see why you would think that now. Let me explain why the free() call is
segfaulting:
#0 0xb7e6bab9 in free () from /lib/tls/li
Falk Hueffner wrote:
> the fact that your program crashes in glibc memory manangement makes
> it quite unlikely that this is a compiler bug. Can you try valgrind?
> Also, your test case is quite large, would it be possible to get
> something smaller?
Then why does it work find with -finline-functi
tags 347697 + moreinfo
thanks
Hi,
the fact that your program crashes in glibc memory manangement makes
it quite unlikely that this is a compiler bug. Can you try valgrind?
Also, your test case is quite large, would it be possible to get
something smaller?
--
Falk
--
To UNSUBSCRIBE, e
6 matches
Mail list logo