public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gmc at synopsys dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/94328] New: Logging of defects to file does not work with Asan and Ubsan combined Date: Wed, 25 Mar 2020 13:46:22 +0000 [thread overview] Message-ID: <bug-94328-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94328 Bug ID: 94328 Summary: Logging of defects to file does not work with Asan and Ubsan combined Product: gcc Version: 6.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: gmc at synopsys dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Created attachment 48114 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48114&action=edit Source code for testcase Compile only with the Address Sanitizer, and the resulting exe can log its defects to file via the log_path setting in ASAN_OPTIONS Ditto for only the Undefined Sanitizer, and using the log_path in UBSAN_OPTIONS Combine the 2 though (the only 2 sanitizers that do seem to be allowed to coexist) and the logging does not seem to work correctly : ASAN_OPTIONS seems to be ignored altogether - and when I set UBSAN_OPTIONS the designated log_path is used ONLY for the Address Sanitizer (incl LeakSanitizer) defects - the Undefined Behavior defects go only to stderr, not to the log file. See attached files : "test.cx" is the source, "make all" builds 3 exes, "run" runs each, with log_path being set via the *_OPTIONS settings Thanks for any help in addressing this. Gordon
next reply other threads:[~2020-03-25 13:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-25 13:46 gmc at synopsys dot com [this message] 2020-03-25 13:46 ` [Bug sanitizer/94328] " gmc at synopsys dot com 2020-03-25 13:47 ` gmc at synopsys dot com 2020-03-25 14:02 ` marxin at gcc dot gnu.org 2020-03-25 14:15 ` gmc at synopsys dot com 2020-03-25 14:18 ` gmc at synopsys dot com 2020-03-25 14:23 ` marxin at gcc dot gnu.org 2020-03-25 14:37 ` marxin at gcc dot gnu.org 2020-03-26 10:06 ` marxin at gcc dot gnu.org 2022-10-14 9:19 ` shanchuantian at gmail dot com 2022-10-14 9:54 ` marxin at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-94328-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).