[ivette] Display lvalues through pointers and pretty offsetmaps

See merge request frama-c/frama-c!3436

Maxime Jacquemin authored 3 years ago and David Bühler committed 3 years ago

We have the same behavior as in the previous GUI. We are going to
discuss about potential improvements.

Maxime Jacquemin authored 3 years ago and David Bühler committed 3 years ago

We have a request that returns all the lvalues pointed by a pointer.

Remove legacy WP engine

See merge request frama-c/frama-c!3438

[ivette] Better visualization of the selected expressions

See merge request frama-c/frama-c!3413

When the layout changes, the model fires the 'laidout' event.
The number of rows may have changed (when callstacks are shown or hidden, for
instance), and the values panel must be updated accordingly.

Maxime Jacquemin authored 3 years ago and David Bühler committed 3 years ago

It is a minor detail

Maxime Jacquemin authored 3 years ago and David Bühler committed 3 years ago

The bug was that a clic on the by callstack button would not display the
values of all callstacks, instead showing only the consolidated one and
a unique callstack. A second clic was necessary to perform the request,
update the caches and finally display the complete data.

The fix we use here is quite brutal: we invalidate the values cache in
the model. I would like to find a cleaner way.

Maxime Jacquemin authored 3 years ago and David Bühler committed 3 years ago

The Valuecomponent had lots of weird bugs, triggering the warning
<Can't perform a React state update on an unmounted component>.
This was caused by an ugly, full of unsafe effect, way to handle the
Model used by a lot of components used by the ValueComponent

Now, the Model is created only once by the ValueComponent itself, and
given as a property to every component that needs it.

As a consequence, the useModel() function is now useless.

[ivette] Messages panel: show complete message in a bottom foldable panel.

See merge request frama-c/frama-c!3433