Skip to content

Commit

Permalink
Use arch of the analizer machine instead of the original one.
Browse files Browse the repository at this point in the history
When creating the content of the ctu-dir the target architecture was
used to which compilation happened. If the analysis runs on a different
architecture (e.g. for debugging reasons) then the analyzer can't find
the necessary files of which the paths are named after the architecture.
  • Loading branch information
bruntib committed Jan 22, 2018
1 parent 58caed9 commit a66a4e5
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions libcodechecker/analyze/ctu_manager.py
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@
import glob
import multiprocessing
import os
import platform
import shutil
import signal
import sys
Expand Down Expand Up @@ -196,9 +197,7 @@ def collect_build_action(params):
analyzer_environment = analyzer_env.get_check_env(
context.path_env_extra,
context.ld_lib_path_extra)
triple_arch = ctu_triple_arch.get_triple_arch(action, source,
config,
analyzer_environment)
triple_arch = platform.machine()
if not config.ctu_in_memory:
generate_ast(triple_arch, action, source, config,
analyzer_environment)
Expand Down

0 comments on commit a66a4e5

Please sign in to comment.