This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Memory problems in GCC ? (found with Valgrind)


Matthieu Moy wrote:-

> ==29106== Invalid read of size 1
> ==29106==    at 0x832ADC4: handle_newline (/home/moy/gcc/src/gcc/cpplex.c:122)
> ==29106==    by 0x832BB20: _cpp_lex_direct (/home/moy/gcc/src/gcc/cpplex.c:933)
> ==29106==    by 0x832B9D9: _cpp_lex_token (/home/moy/gcc/src/gcc/cpplex.c:824)
> ==29106==    by 0x832E1C2: cpp_get_token (/home/moy/gcc/src/gcc/cppmacro.c:1037)
> ==29106==    Address 0x4144B0C0 is not stack'd, malloc'd or free'd
> ==29106== 
> ==29106== Invalid read of size 1
> ==29106==    at 0x832BA62: _cpp_lex_direct (/home/moy/gcc/src/gcc/cpplex.c:893)
> ==29106==    by 0x832B9D9: _cpp_lex_token ( /home/moy/gcc/src/gcc/cpplex.c:824)
> ==29106==    by 0x832E1C2: cpp_get_token ( /home/moy/gcc/src/gcc/cppmacro.c:1037)
> ==29106==    by 0x811C582: c_lex (/home/moy/gcc/src/gcc/c-lex.c:776)
> ==29106==    Address 0x4144B0C0 is not stack'd, malloc'd or free'd

Those are false positives.  I imagine the rest are genuine bugs.

Neil.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]