New issue
Advanced search Search tips

Issue 839939 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 648042



Sign in to add a comment

Problem with setup script/documentation for testing fuzzers locally

Project Member Reported by metzman@chromium.org, May 4 2018

Issue description

As reported by Maksim, following the current instructions results in this error:

==220656==WARNING: Can't read from symbolizer at fd 3
/usr/bin/llvm-symbolizer: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
==220656==WARNING: external symbolizer didn't start up correctly!

We agreed offline that the fix is to copy libtinfo.so.5 into the build chroot


 
Blocking: 648042
Labels: OS-Chrome
Project Member

Comment 3 by bugdroid1@chromium.org, May 11 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/0db9f061b85f677da8c6d5ae95e02362da05d7ea

commit 0db9f061b85f677da8c6d5ae95e02362da05d7ea
Author: Caroline Tice <cmtice@google.com>
Date: Fri May 11 02:40:50 2018

cros_fuzz_test_env: Copy libs for llvm-symbolizer to sysroot.

Make sure that all the libraries necessary for llvm-symbolizer
are copied to the sysroot.

BUG= chromium:839939 
TEST=Ran script successfully, file was copied.

Change-Id: I898629b282076343846f7cf4098aa015c1c26f8d
Reviewed-on: https://chromium-review.googlesource.com/1045102
Commit-Ready: Caroline Tice <cmtice@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/0db9f061b85f677da8c6d5ae95e02362da05d7ea/scripts/cros_fuzz_test_env.py
[modify] https://crrev.com/0db9f061b85f677da8c6d5ae95e02362da05d7ea/lib/osutils.py

Project Member

Comment 4 by bugdroid1@chromium.org, May 11 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7e4547a7ca2bf1becc4a9dfa4b246cd2153c01e5

commit 7e4547a7ca2bf1becc4a9dfa4b246cd2153c01e5
Author: chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Fri May 11 04:15:20 2018

Roll src/third_party/chromite/ 5d1262780..0db9f061b (1 commit)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/5d1262780b26..0db9f061b85f

$ git log 5d1262780..0db9f061b --date=short --no-merges --format='%ad %ae %s'
2018-05-04 cmtice cros_fuzz_test_env: Copy libs for llvm-symbolizer to sysroot.

Created with:
  roll-dep src/third_party/chromite
BUG= chromium:839939 


The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I0fe7472ccb0e8c6074468661c314b6b224aedafa
Reviewed-on: https://chromium-review.googlesource.com/1055108
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#557787}
[modify] https://crrev.com/7e4547a7ca2bf1becc4a9dfa4b246cd2153c01e5/DEPS

Comment 5 by cmt...@chromium.org, May 11 2018

Status: Fixed (was: Untriaged)

Comment 6 by cmt...@chromium.org, May 15 2018

Status: Verified (was: Fixed)
Status: Assigned (was: Verified)
The symlink installed is broken.

$ sudo chroot chroot/build/amd64-generic /bin/bash

$ ls -lt /usr/bin/llvm-symbolizer       
lrwxrwxrwx 1 root root 127 May 15 20:48 /usr/bin/llvm-symbolizer -> /usr/local/google/home/manojgupta/host_migration/chroot/build/amd64-generic/usr/libexec/llvm-symbolizer/usr/bin/llvm-symbolizer

It should be pointing to /usr/libexec/llvm-symbolizer/usr/bin/llvm-symbolizer

Probably using the relative path is better ../../usr/libexec/llvm-symbolizer/usr/bin/llvm-symbolizer.

Comment 9 by cmt...@chromium.org, May 15 2018

Please open a new bug; don't keep re-opening the old one.
Status: Verified (was: Assigned)
Sure, Opened 843340.

Sign in to add a comment