https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
Stewart Martin-Haugh changed:
What|Removed |Added
CC||stewart.martin-haugh at cern
dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
--- Comment #8 from Kostya Serebryany ---
(In reply to Daniel Pinol from comment #7)
> thank you everybody for your great feedback!
>
> @kostya: I provide here the full log. Even removing the #if's, it still
> aborts. strict_memcmp=0 worked like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
--- Comment #7 from Daniel Pinol ---
thank you everybody for your great feedback!
@kostya: I provide here the full log. Even removing the #if's, it still aborts.
strict_memcmp=0 worked like a charm. Thanks!
I guess there's no way to just report
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
--- Comment #6 from Jakub Jelinek ---
(In reply to Daniel Pinol from comment #3)
> #if defined(__has_feature)
> # if __has_feature(address_sanitizer)
> __attribute__((no_sanitize_address))
> # endif
> #endif
> void triggerLang(ReemWindo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
--- Comment #5 from Kostya Serebryany ---
Also check if strict_memcmp=0 helps you.
https://code.google.com/p/address-sanitizer/wiki/Flags
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
--- Comment #4 from Kostya Serebryany ---
Note that the blacklist can not disable the checking inside the memcmp
interceptor. But it will disable instrumenting globals in QT, so
if this is a global from QT (you did not post the full log) you wil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
--- Comment #3 from Daniel Pinol ---
I agree with Kostya.
I get an error within Qt, and I cannot modify its source code. Another option
would be having a flag for not aborting execution when an error is detected (as
in valgrind)
I tried adding
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
--- Comment #2 from Kostya Serebryany ---
Yea. This has been discussed a couple of times before.
using an attribute in the source is clearly the preferable way.
Unfortunately, it is not always technically possible, so we *have* to use the
black
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61978
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
11 matches
Mail list logo
