Re: [Rlib-devel] Re: Crasher bug in RLIB

[Zoltan B. <zb...@du...>]

William K. Volkman =EDrta:
> On Thu, 2005-06-23 at 23:25, Zoltan Boszormenyi wrote:
>=20
>>Bad news. Running the same report in a for() cycle, it still
>>crashes on the second turn. There are more stack-destroying bugs
>>in heaven and earth, Horatio... :-)
>=20
>=20
> I also ran into this last night, haven't had a chance to

Phew. So it's not just my bad luck. :-)

> investigate further.  Are you using your two patches
> for the GCC 4 issues?  My RLIB version is skewed a bit

Yes, I am using those two patches, and I also cleaned up
"long long" usage replacing it with gint64 abstract type
to further reduce the amount of warnings. It would be best
to get rid of all the explicit casts so the compiler's
type checking will work.

> from latest CVS, 3 of the last 5 patches I made
> are not in CVS yet.  I might get some time this weekend
> to help you hunt the other bugs.

I intend to install the final gcc-4.0.0 (the gcc4 update for FC3
is based on a snapshot) and the bounds checking patch on top of it.
This seems to be a highly useful feature, you can find it here:

http://sourceforge.net/projects/boundschecking/

The compiler will generate code that guards against itself
if you use option -fbounds-checking. Valgrind for x86-64
(daily subversion repository) starts working again
but it does not catch stack corruption. :-(
Thanks, anyway.

Best regards,
Zolt=E1n B=F6sz=F6rm=E9nyi