Skip to content

Possibly better handling of MSAN reports #863

@LebedevRI

Description

@LebedevRI

I may be completely wrong here, but i'm under the impression that currently the reports
from memory sanitizer are deduplicated by the "Crash State", and then reported, correct?

Consider the following pseudo-code:

// both functions do some different stuff with memory
// but both of them do *not* init all of the memory
void f0(char* mem); 
void f1(char* mem);

int main(int argc, char* argv[]) {
  char buf[32];

  if(argc == 1)
   f0(&buf[0]);
  else
   f1(&buf[0]);

  __msan_check_mem_is_initialized(&buf[0], sizeof(buf)); // ta-da!
}

There are two distinct problems, but currently i believe oss-fuzz would only report one,
and only after it is fixed, report the second-one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions