Project

General

Profile

Actions
Copy link

Feature #6880

closed

Investigate what dependent modules should be analysed together to find well known bugs

Added by Evgeny Novikov about 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
High
Assignee:
Alexey Polushkin
Category:
Program fragments generation
Target version:
-
Start date:
02/19/2016
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Published in build:

Description

Instead of constructing artificial strategies for generating multi-module verification objects that likely will not give us much positive, I suggest to investigate what dependent modules should be analysed together to find well known bugs.

This issue is intended to join several such cases together. I think that each case should be considered in a separate issue since all they will be quite individual and can be supported with various strategies implemented step by step.

Subtasks 3 (0 open — 3 closed)

Feature #6881: Example of multi-module dependency within one directoryClosedAlexey Polushkin02/19/2016

Actions
Feature #6884: Example of multi-module dependency for detecting data racesClosedAlexey Polushkin02/19/2016

Actions
Feature #6955: Example of target bug that can not be found without multi-module analysisClosedAlexey Polushkin03/10/2016

Actions
Actions
Copy link
 #1

Updated by Evgeny Novikov almost 8 years ago

  • Status changed from New to Closed

The topic is inexhaustible but all sub-tasks were completed.

Actions
Copy link

Also available in: Atom PDF