Whitespace difference between asan and msan outputs

[GoogleCodeExporter]

ASAN and MSAN should have same output format, but there is a whitespace missing 
from ASAN output after ==$PID==.

Sample ASAN output:(Chrome prebuild)

==31212==ERROR: AddressSanitizer: heap-buffer-overflow ...

> asan_output.split(' ')
[ '==31212==ERROR:',
  'AddressSanitizer:',
  'heap-buffer-overflow' ]

Sample MSAN output:(Chrome prebuild)

==18899== WARNING: MemorySanitizer: use-of-uninitialized-value ...

> msan_output.split(' ')
[ '==18899==',
  'WARNING:',
  'MemorySanitizer:',
  'use-of-uninitialized-value' ]

This issue prevents usage of same parser, that uses whitespace splitting, for 
both ASAN and MSAN outputs without additional checks.

Original issue reported on code.google.com by attek...@gmail.com on 31 Mar 2015 at 2:49

[GoogleCodeExporter]

I wonder if fixing this will break someone else's scripts. 
But I agree, we should make these similar. 

Original comment by konstant...@gmail.com on 31 Mar 2015 at 5:57

[GoogleCodeExporter]

Looking.

Original comment by samso...@google.com on 31 Mar 2015 at 6:15

• Changed state: Started

[GoogleCodeExporter]

r233720

Original comment by samso...@google.com on 31 Mar 2015 at 6:19

• Changed state: Fixed

[GoogleCodeExporter]

Adding Project:AddressSanitizer as part of GitHub migration.

Original comment by ramosian.glider@gmail.com on 30 Jul 2015 at 9:14

• Added labels: ProjectAddressSanitizer