Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

analyze --capture-analysis-output writes corrupt zipfiles

See original GitHub issue

Describe the bug At the end of analyze, I see hundreds of the following warnings:

/usr/lib/python3.8/ UserWarning: Duplicate name: 'sources-root/home/cc-runs/src/qt/qt5/qtbase/src/printsupport/kernel/qprint_p.h'
  return self._open_to_write(zinfo, force_zip64=force_zip64)

The zipfiles stored under results_dir/run_name/failed are troublesome to unzip. On linux with the unzip command I am asked countless of times whether I want to overwrite certain files.

CodeChecker version is today’s latest HEAD at d78f1d9306868669ec07b8996c2cec1d29a664a3.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10 (6 by maintainers)

github_iconTop GitHub Comments

csordasmartoncommented, Dec 16, 2020

You can use the following option of the CodeChecker analyze command:

--file FILE [FILE ...]
                        Analyze only the given file(s) not the whole
                        compilation database. Absolute directory paths should
                        start with '/', relative directory paths should start
                        with '*' and it can contain path glob pattern.
                        Example: '/path/to/main.cpp', 'lib/*.cpp', */test*'.
jimiscommented, Dec 29, 2020

Do you have the standard output and error logs related to the analysis of qdatetime.cpp file?

Because in your zip file name I can see the unknown keyword which comes from this code:

So the problem is not a compiler crash or a compiler error. I am curious what it can be.

So as you can see in the log, the error is:

/usr/include/c++/9/array:245:28: error: cannot import unsupported AST node CXXFoldExpr
      -> array<enable_if_t<(is_same_v<_Tp, _Up> && ...), _Tp>,

The return code cannot be seen in the log, but in the file return-code I see -11.

As mentioned earlier, this has been reported at #3012 (see 2nd point in description). It is blocking CTU analysis for C++17 projects.

But how is it related to the corrupted zipfiles issue?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Methods to Extract Data from Corrupt ZIP File
Step 1 Launch File Repair Tool and select the "Repair ZIP File" option start to repairing the process. Step 2 Search corrupt ZIP...
Read more >
Unzipping corrupted zip file - Oracle Communities
I have a corrupted zip file whose contents I'm trying to salvage. I know that the problem is with one of the files...
Read more >
java - How to check if a generated zip file is corrupted?
You can use the ZipFile class to check your file : static boolean isValid(final File file) { ZipFile zipfile = null; try {...
Read more >
ZIPs tricks - HackTricks
There are a handful of command-line tools for zip files that will be useful ... zip -FF --out attempt to repair...
Read more >
Analysis of Data Source Using Autopsy - GeeksforGeeks
The Sleuth Kit is a library and a collection of command-line tools used to investigate disk images. Autopsy is the GUI program for...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found