Project

General

Profile

Actions

Feature #7639

closed

Visualize actions of environment model scenarios

Added by Evgeny Novikov over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Immediate
Category:
Bridge
Target version:
-
Start date:
10/26/2016
Due date:
11/16/2016
% Done:

0%

Estimated time:
Published in build:

Description

Now we almost finish a new error trace format. There are 2 new entities: actions and callback actions. The first entity is represented as an array of comments where array indexes correspond to action identifiers. Edges belonging to corresponding actions are additionally marked with attribute action. The second entity is represented as a set of identifiers of actions of the first kind.

Actions aren't notes and their visualization does differ since one action can cover multiple edges. Ilja suggested to visualize actions like auxiliary functions with notes. But this isn't good enough. It does has sense to increase offsets for edges of actions by 1 and to have narrows to show/hide these edges like for functions. But edges with notes and warnings that lie below actions in their stacks shouldn't be hidden like for nested notes.

Callback actions shouldn't be distinguished much here except corresponding comments can be bold. They have much sense for another issue I will open soon.


Files

error trace.json.tar.gz (22.7 KB) error trace.json.tar.gz Evgeny Novikov, 10/26/2016 06:20 PM
error trace.json.tar.gz (76.1 KB) error trace.json.tar.gz Evgeny Novikov, 10/31/2016 02:52 PM

Related issues 1 (0 open1 closed)

Blocks Klever - Feature #7640: By default hide all edges from error traces without important annotationsClosedVladimir Gratinskiy10/26/201611/16/2016

Actions
Actions #1

Updated by Vladimir Gratinskiy over 7 years ago

Is the error trace in the attached archive valid? I suppose "ldv_xmalloc" missed 'enter' somewhere.

Upd: error trace is valid. Can I have one more error trace - without threads?

Actions #2

Updated by Evgeny Novikov over 7 years ago

Let's try another one that is successfully generated and visualized without any warnings. If there will be still some issues it would be better to reject such broken error traces.

Actions #3

Updated by Vladimir Gratinskiy over 7 years ago

  • Due date set to 11/16/2016
  • Status changed from New to Resolved

Implemented in branch 'better-unsafes-and-marks'.

Actions #4

Updated by Ilja Zakharov over 7 years ago

  • Status changed from Resolved to Closed

Merged in 6e2305dc.

Actions

Also available in: Atom PDF