Project

General

Profile

Actions
Copy link

Feature #1703

closed

Think about error trace traversing library

Added by Evgeny Novikov almost 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
High
Assignee:
Evgeny Novikov
Category:
Infrastructure
Start date:
08/29/2011
Due date:
% Done:

0%

Estimated time:
Published in build:
082feed

Description

It'll help to implement KB library and may be used, for instance, to deal with issues like #946.

Related issues 4 (2 open — 2 closed)

Blocked by Linux Driver Verification - Feature #1702: Extract error trace parser from error-trace-visualizerClosedEvgeny Novikov08/29/2011

Actions
Blocks Linux Driver Verification - Feature #1633: KB: library function to check if assertion failed in a function givenOpenEvgeny Novikov08/11/2011

Actions
Blocks Linux Driver Verification - Feature #1637: KB: Check for error trace in default KB patternClosedEvgeny Novikov08/13/2011

Actions
Blocks Linux Driver Verification - Feature #946: Implement intellectual function bodies closing in the more efficient wayOpenEvgeny Novikov03/15/2011

Actions
Actions
Copy link
 #1

Updated by Evgeny Novikov almost 13 years ago

  • Subject changed from Think and implement error trace traversing library to Think about error trace traversing library
  • Priority changed from Normal to High

I'm going to think about its design since it touches #1637 issue as well as some other important issues to be implemented in near future. Also I suggest that implementation should be developed step-by-step in depend on particular requests.

Actions
Copy link
 #2

Updated by Evgeny Novikov almost 13 years ago

  • Status changed from Open to Resolved

It's done in 082feed commit. At the moment error trace browser is included into error trace visualizer shared modules. This module contains special routines that can extract some needed information from internal error trace representation as well as routines that for instance can deal with this extracted information (compare, debug, etc.).
Further development of error trace browser should be done when it'll be required by some new feature(s).

Actions
Copy link
 #3

Updated by Evgeny Novikov almost 13 years ago

  • Status changed from Resolved to Closed
  • Published in build set to 6fd6348

It's in master now. May be should be redeveloped after ETV redisigning.

Actions
Copy link
 #4

Updated by Evgeny Novikov almost 13 years ago

  • Published in build changed from 6fd6348 to 082feed
Actions
Copy link

Also available in: Atom PDF