Summary: | sys-devel/gcc: libjava/java/lang/natClass.cc has memcpy overflows | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David J Cozatt <djcozatt> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED UPSTREAM | ||
Severity: | QA | CC: | jlec, Martin.vGagern |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://gcc.gnu.org/PR46632 | ||
See Also: | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46632 | ||
Whiteboard: | upstream wontfix; masked in 17.0 profiles | ||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log.bz2 |
Description
David J Cozatt
2010-11-23 23:21:34 UTC
Created attachment 255263 [details]
build.log.bz2
the actual warning: In file included from /usr/include/string.h:642:0, from /var/tmp/portage/sys-devel/gcc-4.5.1-r1/work/gcc-4.5.1/libjava/java/lang/natClass.cc:15: In function ‘void* memcpy(void*, const void*, size_t)’, inlined from ‘java::lang::Object* parseAnnotationElement(java::lang::Class*, _Jv_Constants*, unsigned char*&, unsigned char*)’ at /var/tmp/portage/sys-devel/gcc-4.5.1-r 1/work/gcc-4.5.1/libjava/java/lang/natClass.cc:1168:60: /usr/include/bits/string3.h:52:71: warning: call to void* __builtin___memcpy_chk(void*, const void*, long unsigned int, long unsigned int) will always overflow destination buffer In function ‘void* memcpy(void*, const void*, size_t)’, inlined from ‘java::lang::Object* parseAnnotationElement(java::lang::Class*, _Jv_Constants*, unsigned char*&, unsigned char*)’ at /var/tmp/portage/sys-devel/gcc-4.5.1-r1/work/gcc-4.5.1/libjava/java/lang/natClass.cc:1184:60: /usr/include/bits/string3.h:52:71: warning: call to void* __builtin___memcpy_chk(void*, const void*, long unsigned int, long unsigned int) will always overflow destination buffer Setting USE="-gcj" emerge gcc worked without the message. Disabling this flag is a temporary workaround The removal of this flag by way of package.use was applied 'emerge -vuNDp world' showed pdftk as needing the flag hence it's use in the first place. did -p --depclean and removed pdftk finding no other problems to applications *** Bug 363065 has been marked as a duplicate of this bug. *** *** Bug 341491 has been marked as a duplicate of this bug. *** I can reproduce the problem with the latest stable (4.8.4). So, since 4.5.1-r1 is not anymore in the tree I'd like to update the summary changing the version. FTR I can reproduce with 4.9.3 too (In reply to Agostino Sarubbo from comment #8) the code hasn't really ever changed, so the bug continues to apply to pretty much every version. upstream doesn't seem to care. |