[Bug sanitizer/88054] Sanitizer triggers on valid code

2018-11-16 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88054 Martin Liška changed: What|Removed |Added See Also||https://sourceware.org/bugz

[Bug sanitizer/88054] Sanitizer triggers on valid code

2018-11-16 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88054 --- Comment #4 from Jakub Jelinek --- The comment is bogus, that is the symbol versioning design, the only way how to stay ABI compatible even with the binaries that were written before the new symbol version has been introduced. For symbols wit

[Bug sanitizer/88054] Sanitizer triggers on valid code

2018-11-16 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88054 --- Comment #3 from Martin Liška --- The problem looks very similar to: 3537 #if SANITIZER_INTERCEPT_REALPATH 3538 INTERCEPTOR(char *, realpath, const char *path, char *resolved_path) { 3539void *ctx; 3540COMMON_INTERCEPTOR_ENT

[Bug sanitizer/88054] Sanitizer triggers on valid code

2018-11-16 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88054 --- Comment #2 from Jakub Jelinek --- Apparently i?86 glibc has two fopen entrypoints: 192: 000657d035 FUNCGLOBAL DEFAULT 13 fopen@@GLIBC_2.1 193: 0011ec90 144 FUNCGLOBAL DEFAULT 13 fopen@GLIBC_2.0 and libsanitizer interce

[Bug sanitizer/88054] Sanitizer triggers on valid code

2018-11-16 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88054 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|