Barry,
Thanks for the report. I have seen a couple things recently that may be
related.
1. Some recent operating systems are now shipping with more aggressive
runtime error checking in the default C libraries, which is finding and
dying on one or more errors in icont in code that has run fine and
hasn't been changed in many years. This is sort of an incompatible change in
the C language, but it is a good thing in most respects, or will be once all
the bugs it finds are fixed.
2. Recently I ran across an icont memory error that was occurring in the
buffer
expanding code -- it was reallocating the main translator string space but
pointers into the old memory buffer were still live. The error disappeared
when I made the initial string buffer size larger, but of course I would
rather fix the bug than hide it.
Having said all this, there have been a few modest changes to icont in 2008
and 2009 that could have altered its footprint enough to have introduced
some new bug, and whether a bug is new or old, the buck stops here.
Sometimes things run fine on those platforms that I have access to, but fail
elsewhere. I will work on fixes for those items that I can reproduce, and
welcome bugfixes contributed by users, or additional details or guest
accounts on machines whose platforms I don't have local access to.
Cheers,
Clint
On Fri, Oct 30, 2009 at 12:09 AM, Barry Schwartz <
chemoelect...@chemoelectric.org> wrote:
> I decided to try compiling the latest CVS and, while the build goes
> through for intel_linux, building amd64_linux (gcc 4.4.2) fails due to
> buffer overflow in icont. Possibly related, there were many warnings
> about broken printf calls, some warnings about potentially dangerous
> casts, etc., that could affect AMD64 or other 64-bit architectures.
>
> (Also I noticed that the Xft tests in aclocal.m4 are out of date and
> won't work with current versions, but AFAICT Xft isn't actually used
> anywhere in the code. :)
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Unicon-group mailing list
> Unicon-group@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unicon-group
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
