[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2023-02-06 Thread fw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #13 from Florian Weimer --- (In reply to Alexander Enaldiev from comment #12) > But here I see status 'RESOLVED FIXED'. Do you presume, my today's issue > isn't connected? It could still be the same bug. It's supposed to be fixed

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2023-02-06 Thread alexander.enaldiev at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 Alexander Enaldiev changed: What|Removed |Added CC||alexander.enaldiev at gmail dot

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-09-11 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |8.5

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-08-05 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 Bug 100114 depends on bug 101749, which changed state. Bug 101749 Summary: gcc -static-libasan broken because libasan.a needs __cxa_guard_release in libstdc++ https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101749 What|Removed

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-22 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #10 from CVS Commits --- The releases/gcc-8 branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:ef195a39d0d3b929cc676302d074b42c25460601 commit r8-10912-gef195a39d0d3b929cc676302d074b42c25460601 Author: Jakub Jelinek

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #9 from CVS Commits --- The releases/gcc-9 branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:3d0135bf3be416bbe2531dc763d19b749eb2b856 commit r9-9450-g3d0135bf3be416bbe2531dc763d19b749eb2b856 Author: Jakub Jelinek

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #8 from CVS Commits --- The releases/gcc-10 branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:950bac27d63c1c2ac3a6ed867692d6a13f21feb3 commit r10-9732-g950bac27d63c1c2ac3a6ed867692d6a13f21feb3 Author: Jakub Jelinek

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 Richard Biener changed: What|Removed |Added Known to work||11.0 --- Comment #7 from Richard

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-17 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #6 from Jakub Jelinek --- Fixed on the trunk so far, guess some backporting will be useful.

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #5 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:d9f462fb372fb02da032cefd6b091d7582c425ae commit r11-8230-gd9f462fb372fb02da032cefd6b091d7582c425ae Author: Jakub Jelinek Date:

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-16 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #4 from Jakub Jelinek --- const vars in C++ can't be uninitialized nor modified. And initializing those in constructor or .init_array is too late, the problem is that the function is called from .preinit_array handler, so before

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-16 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #3 from H.J. Lu --- (In reply to Richard Biener from comment #2) > Confirmed by code inspection, but it's for sure sth not new (but would be > nice to fix before GCC 11.1). > > I suggtest to simply move the initialization inside

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-16 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #2 from Richard Biener --- Confirmed by code inspection, but it's for sure sth not new (but would be nice to fix before GCC 11.1). I suggtest to simply move the initialization inside SetAlternateSignalStack. Sth like diff --git

[Bug sanitizer/100114] libasan built against latest glibc doesn't work

2021-04-16 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114 --- Comment #1 from Jakub Jelinek --- As a quick hack, we could do something like: #ifdef _SC_SIGSTKSZ #define kAltStackSize (SIGSTKSZ * 4) #else static const uptr kAltStackSize = SIGSTKSZ * 4; // SIGSTKSZ is not enough. #endif but the