clustc / google-breakpad

Automatically exported from code.google.com/p/google-breakpad
0 stars 0 forks source link

Cannot pass the "make check" with CentOS-6.5 (gcc-4.4.7, gcc-4.8.2) #600

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. install a new centos-6.5 x86_64
2. get the last svn revision
3. ./configure && make && make check

What is the expected output? What do you see instead?
Under my desktop ubuntu 14.04 LTS (gcc 4.8.2-19ubuntu1) all tests passed 
successful;

What version of the product are you using? On what operating system?
I have tried to use the default version of CentOS gcc - 4.4.7 as well as 
devtoolset-2 with gcc-4.8.2 — the same result has been returned;

Please provide any additional information below.

OUTPUT from src/common/dumper_unittest:

[ RUN      ] ElfCoreDumpTest.ValidCoreFile
src/common/linux/elf_core_dump_unittest.cc:159: Failure
Value of: mapped_core_file.Map(crash_generator.GetCoreFilePath().c_str())
  Actual: false
Expected: true
[  FAILED  ] ElfCoreDumpTest.ValidCoreFile (5 ms)

OUTPUT from src/client/linux/linux_client_unittest:

[ RUN      ] LinuxCoreDumperTest.VerifyDumpWithMultipleThreads
Could not map core dump file into memory
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:94: Failure
Value of: dumper.Init()
  Actual: false
Expected: true
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:105: Failure
Value of: dumper.crash_signal()
  Actual: 0
Expected: kCrashSignal
Which is: 6
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:107: Failure
Value of: dumper.crash_thread()
  Actual: 8149
Expected: crash_generator.GetThreadId(kCrashThread)
Which is: 8150
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:109: Failure
Value of: dumper.threads().size()
  Actual: 0
Expected: kNumOfThreads
Which is: 3
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:112: Failure
Value of: dumper.GetThreadInfoByIndex(i, &info)
  Actual: false
Expected: true
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:115: Failure
Value of: dumper.GetStackInfo(&stack, &stack_len, info.stack_pointer)
  Actual: false
Expected: true
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:116: Failure
Value of: info.ppid
  Actual: 0
Expected: getpid()
Which is: 8088
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:112: Failure
Value of: dumper.GetThreadInfoByIndex(i, &info)
  Actual: false
Expected: true
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:115: Failure
Value of: dumper.GetStackInfo(&stack, &stack_len, info.stack_pointer)
  Actual: false
Expected: true
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:116: Failure
Value of: info.ppid
  Actual: 0
Expected: getpid()
Which is: 8088
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:112: Failure
Value of: dumper.GetThreadInfoByIndex(i, &info)
  Actual: false
Expected: true
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:115: Failure
Value of: dumper.GetStackInfo(&stack, &stack_len, info.stack_pointer)
  Actual: false
Expected: true
src/client/linux/minidump_writer/linux_core_dumper_unittest.cc:116: Failure
Value of: info.ppid
  Actual: 0
Expected: getpid()
Which is: 8088
[  FAILED  ] LinuxCoreDumperTest.VerifyDumpWithMultipleThreads (3 ms)

By the way, as root user you'll get segfault at start of application 
linux_client_unittest. Thus I have run build process as normal user and got 
these issues. Any idea why this could happen?

Thanks,
Roman.

Original issue reported on code.google.com by roman.go...@gmail.com on 10 Jul 2014 at 5:11