New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 825359 link

Starred by 3 users
Status: Fixed
Owner:
mmoroz@chromium.org
Closed: Apr 2018
Cc:
█ robert...@chromium.org
liaoyuke@chromium.org
mmoroz@chromium.org
infe...@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 759794



Sign in to add a comment

Investigate why same binary can have different module signatures (i.e. different %Nm pools)

Project Member Reported by mmoroz@chromium.org, Mar 23 2018 
I printf-debud'ed some data for viz_unittests binary, which creates profile files with two different module signatures:

1) https://paste.googleplex.com/5714782241947648

2) https://paste.googleplex.com/5755523227975680

This issue is not a blocker, but I don't feel comfortable not understanding the root cause.

Comment 1 by mmoroz@chromium.org, Apr 14 2018

Owner: mmoroz@chromium.org
Status: Fixed (was: Untriaged)
And now after working on  issue 831939  I know where are those different module signatures from -- those are from different binaries including shared libraries. 

It appears that we have some shared libraries even in case of a non component build. That means that we might be missing some coverage unless we pass those libraries to the llvm-cov command. I have a WIP patch in  issue 831939 , will test it on a bot with a bunch of targets.
►

Sign in to add a comment