Groups

memory-sanitizer

1–30 of 68

0 selected

5/12/22

Re: Simple program segfaults when ThreadSanitizer is enabled

On Thu, 12 May 2022 at 14:25, Olivier Nicole <oli...@tarides.com> wrote: > > I forgot to

unread,

Re: Simple program segfaults when ThreadSanitizer is enabled

On Thu, 12 May 2022 at 14:25, Olivier Nicole <oli...@tarides.com> wrote: > > I forgot to

5/12/22

10/5/21

Re: Thread Sanitizer could not print proper stack trace.

On Wed, 22 Sept 2021 at 10:14, Dmitry Vyukov <dvy...@google.com> wrote: > > +thread-

unread,

Re: Thread Sanitizer could not print proper stack trace.

On Wed, 22 Sept 2021 at 10:14, Dmitry Vyukov <dvy...@google.com> wrote: > > +thread-

10/5/21

7/18/20

Re: TSan "Nested bug" intermittent failure

Maybe this symbolizer warning is just a red herring, hard to say. I've tried to create very long

unread,

Re: TSan "Nested bug" intermittent failure

Maybe this symbolizer warning is just a red herring, hard to say. I've tried to create very long

7/18/20

Evgenii Stepanov3

3/16/20

Re: MSan: Uninitialized Memory in do_sys_mknodat

Thanks. I've reduced and filed https://bugs.llvm.org/show_bug.cgi?id=45220 Not sure what to do

unread,

Re: MSan: Uninitialized Memory in do_sys_mknodat

Thanks. I've reduced and filed https://bugs.llvm.org/show_bug.cgi?id=45220 Not sure what to do

3/16/20

nolo...@gmail.com, Evgenii Stepanov2

5/8/19

Trouble building package with Msan

MSan runtime library is statically linked to the executable, and its symbols are re-exported. There

unread,

Trouble building package with Msan

MSan runtime library is statically linked to the executable, and its symbols are re-exported. There

5/8/19

Wink Saville, Evgenii Stepanov6

9/13/16

-fsanitize=memory failing on an Arch Linux system

So it sounds like this problem should be reproducible on ToT glibc, and it should affect other

unread,

-fsanitize=memory failing on an Arch Linux system

So it sounds like this problem should be reproducible on ToT glibc, and it should affect other

9/13/16

Jeffrey Walton, … Evgenii Stepanov10

2/29/16

FATAL: MemorySanitizer can not mmap the shadow memory.

This could be caused by disabled ASLR, you could try sysctl -w kernel.randomize_va_space=0 and the

unread,

FATAL: MemorySanitizer can not mmap the shadow memory.

This could be caused by disabled ASLR, you could try sysctl -w kernel.randomize_va_space=0 and the

2/29/16

nolo...@gmail.com, … Evgenii Stepanov4

2/29/16

How to unpoison a C++ std::string?

Also, use -fsanitize-memory-track-origins, it adds lots of useful info to the reports. On Sun, Feb 28

unread,

How to unpoison a C++ std::string?

Also, use -fsanitize-memory-track-origins, it adds lots of useful info to the reports. On Sun, Feb 28

2/29/16

nolo...@gmail.com, Konstantin Serebryany2

2/27/16

How to detect when -fsanitize=memory is in effect?

You need this: http://clang.llvm.org/docs/MemorySanitizer.html#has-feature-memory-sanitizer On Sat,

unread,

How to detect when -fsanitize=memory is in effect?

You need this: http://clang.llvm.org/docs/MemorySanitizer.html#has-feature-memory-sanitizer On Sat,

2/27/16

memory-s...@googlecode.com2

8/4/15

Issue 90 in memory-sanitizer: Use-after-dtor thread reporting

Comment #1 on issue 90 by konstant...@gmail.com: Use-after-dtor thread reporting https://code.google.

unread,

Issue 90 in memory-sanitizer: Use-after-dtor thread reporting

Comment #1 on issue 90 by konstant...@gmail.com: Use-after-dtor thread reporting https://code.google.

8/4/15

memory-s...@googlecode.com

7/21/15

Issue 89 in memory-sanitizer: Use-after-dtor reports are hard to read

Status: New Owner: nmusgr...@google.com CC: euge...@google.com, k...@google.com Labels: Type-Defect

unread,

Issue 89 in memory-sanitizer: Use-after-dtor reports are hard to read

Status: New Owner: nmusgr...@google.com CC: euge...@google.com, k...@google.com Labels: Type-Defect

7/21/15

memory-s...@googlecode.com2

6/18/15

Issue 86 in memory-sanitizer: Intercept fopencookie

Updates: Status: Fixed Comment #1 on issue 86 by euge...@google.com: Intercept fopencookie https://

unread,

Issue 86 in memory-sanitizer: Intercept fopencookie

Updates: Status: Fixed Comment #1 on issue 86 by euge...@google.com: Intercept fopencookie https://

6/18/15

memory-s...@googlecode.com

6/8/15

Re: Issue 43 in memory-sanitizer: Enable check_printf=1 by default

Updates: Summary: Enable check_printf=1 by default Comment #1 on issue 43 by euge...@google.com:

unread,

Re: Issue 43 in memory-sanitizer: Enable check_printf=1 by default

Updates: Summary: Enable check_printf=1 by default Comment #1 on issue 43 by euge...@google.com:

6/8/15

memory-s...@googlecode.com2

4/6/15

Issue 87 in memory-sanitizer: False negative with stack slot reuse

Comment #1 on issue 87 by euge...@google.com: False negative with stack slot reuse https://code.

unread,

Issue 87 in memory-sanitizer: False negative with stack slot reuse

Comment #1 on issue 87 by euge...@google.com: False negative with stack slot reuse https://code.

4/6/15

memory-s...@googlecode.com6

3/27/15

Issue 88 in memory-sanitizer: msan false positive when using std::{cout|cerr|clog}.

Updates: Status: Invalid Comment #5 on issue 88 by euge...@google.com: msan false positive when using

unread,

Issue 88 in memory-sanitizer: msan false positive when using std::{cout|cerr|clog}.

Updates: Status: Invalid Comment #5 on issue 88 by euge...@google.com: msan false positive when using

3/27/15

memory-s...@googlecode.com10

2/25/15

Issue 85 in memory-sanitizer: Add MacOs support

Comment #9 on issue 85 by gonzalob...@gmail.com: Add MacOs support https://code.google.com/p/memory-

unread,

Issue 85 in memory-sanitizer: Add MacOs support

Comment #9 on issue 85 by gonzalob...@gmail.com: Add MacOs support https://code.google.com/p/memory-

2/25/15

memory-s...@googlecode.com2

1/29/15

Issue 84 in memory-sanitizer: VectorMaddTest.mmx_pmadd_wd is broken

Updates: Status: Invalid Comment #1 on issue 84 by euge...@google.com: VectorMaddTest.mmx_pmadd_wd is

unread,

Issue 84 in memory-sanitizer: VectorMaddTest.mmx_pmadd_wd is broken

Updates: Status: Invalid Comment #1 on issue 84 by euge...@google.com: VectorMaddTest.mmx_pmadd_wd is

1/29/15

memory-s...@googlecode.com6

1/27/15

Issue 76 in memory-sanitizer: Ultra-compatible memory mapping

Comment #5 on issue 76 by euge...@google.com: Ultra-compatible memory mapping https://code.google.com

unread,

Issue 76 in memory-sanitizer: Ultra-compatible memory mapping

Comment #5 on issue 76 by euge...@google.com: Ultra-compatible memory mapping https://code.google.com

1/27/15

memory-s...@googlecode.com9

1/27/15

Issue 54 in memory-sanitizer: False positives with qsort, std::stringstream, and AVX

Comment #8 on issue 54 by euge...@google.com: False positives with qsort, std::stringstream, and AVX

unread,

Issue 54 in memory-sanitizer: False positives with qsort, std::stringstream, and AVX

Comment #8 on issue 54 by euge...@google.com: False positives with qsort, std::stringstream, and AVX

1/27/15

memory-s...@googlecode.com2

1/27/15

Issue 83 in memory-sanitizer: getlogin_r + strlen false positive

Updates: Status: Accepted Owner: euge...@google.com Comment #1 on issue 83 by euge...@google.com:

unread,

Issue 83 in memory-sanitizer: getlogin_r + strlen false positive

Updates: Status: Accepted Owner: euge...@google.com Comment #1 on issue 83 by euge...@google.com:

1/27/15

memory-s...@googlecode.com

1/26/15

Issue 82 in memory-sanitizer: Origin lost in unaligned memcpy

Status: Accepted Owner: euge...@google.com Labels: Type-Defect Priority-Medium New issue 82 by euge..

unread,

Issue 82 in memory-sanitizer: Origin lost in unaligned memcpy

Status: Accepted Owner: euge...@google.com Labels: Type-Defect Priority-Medium New issue 82 by euge..

1/26/15

memory-s...@googlecode.com2

1/22/15

Issue 81 in memory-sanitizer: Intercept sched_getparam

Updates: Status: Fixed Comment #1 on issue 81 by euge...@google.com: Intercept sched_getparam https:/

unread,

Issue 81 in memory-sanitizer: Intercept sched_getparam

Updates: Status: Fixed Comment #1 on issue 81 by euge...@google.com: Intercept sched_getparam https:/

1/22/15

memory-s...@googlecode.com6

1/22/15

Re: Issue 35 in memory-sanitizer: Find a better name for origin coming from free()

Updates: Status: Fixed Comment #6 on issue 35 by euge...@google.com: Find a better name for origin

unread,

Re: Issue 35 in memory-sanitizer: Find a better name for origin coming from free()

Updates: Status: Fixed Comment #6 on issue 35 by euge...@google.com: Find a better name for origin

1/22/15

memory-s...@googlecode.com4

1/21/15

Issue 73 in memory-sanitizer: MsanReallocate does not handle origins correctly

Updates: Status: Fixed Comment #3 on issue 73 by euge...@google.com: MsanReallocate does not handle

unread,

Issue 73 in memory-sanitizer: MsanReallocate does not handle origins correctly

Updates: Status: Fixed Comment #3 on issue 73 by euge...@google.com: MsanReallocate does not handle

1/21/15

memory-s...@googlecode.com

1/21/15

Re: Issue 6 in memory-sanitizer: Issues in origin handling

Updates: Cc: earth...@google.com Comment #4 on issue 6 by euge...@google.com: Issues in origin

unread,

Re: Issue 6 in memory-sanitizer: Issues in origin handling

Updates: Cc: earth...@google.com Comment #4 on issue 6 by euge...@google.com: Issues in origin

1/21/15

memory-s...@googlecode.com2

1/21/15

Re: Issue 62 in memory-sanitizer: Origin tracking is not async signal safe

Updates: Status: Fixed Comment #4 on issue 62 by euge...@google.com: Origin tracking is not async

unread,

Re: Issue 62 in memory-sanitizer: Origin tracking is not async signal safe

Updates: Status: Fixed Comment #4 on issue 62 by euge...@google.com: Origin tracking is not async

1/21/15

memory-s...@googlecode.com

1/14/15

Issue 80 in memory-sanitizer: SUMMARY: MemorySanitizer: use-of-uninitialized-value ??:0 ??

Status: New Owner: ---- CC: earth...@google.com Labels: Type-Defect Priority-Medium New issue 80 by

unread,

Issue 80 in memory-sanitizer: SUMMARY: MemorySanitizer: use-of-uninitialized-value ??:0 ??

Status: New Owner: ---- CC: earth...@google.com Labels: Type-Defect Priority-Medium New issue 80 by

1/14/15

memory-s...@googlecode.com

1/14/15

Issue 79 in memory-sanitizer: Check interceptor parameters for initializedness

Status: New Owner: ---- CC: earth...@google.com Labels: Type-Defect Priority-Medium New issue 79 by

unread,

Issue 79 in memory-sanitizer: Check interceptor parameters for initializedness

Status: New Owner: ---- CC: earth...@google.com Labels: Type-Defect Priority-Medium New issue 79 by

1/14/15

memory-s...@googlecode.com2

12/1/14

Issue 77 in memory-sanitizer: Get rid of getCleanOrigin()

Updates: Status: Fixed Comment #1 on issue 77 by euge...@google.com: Get rid of getCleanOrigin()

unread,

Issue 77 in memory-sanitizer: Get rid of getCleanOrigin()

Updates: Status: Fixed Comment #1 on issue 77 by euge...@google.com: Get rid of getCleanOrigin()

12/1/14

memory-s...@googlecode.com2

11/28/14

Issue 78 in memory-sanitizer: select i1, float, float loses origins for the last two arguments

Updates: Status: Fixed Comment #1 on issue 78 by euge...@google.com: select i1, float, float loses

unread,

Issue 78 in memory-sanitizer: select i1, float, float loses origins for the last two arguments

Updates: Status: Fixed Comment #1 on issue 78 by euge...@google.com: select i1, float, float loses

11/28/14

Search

Clear search

Close search

Google apps

Main menu