vite issueshttps://gitlab.inria.fr/solverstack/vite/-/issues2023-07-09T00:21:35+02:00https://gitlab.inria.fr/solverstack/vite/-/issues/25clang-format2023-07-09T00:21:35+02:00Johnny Jazeixclang-formathttps://gitlab.inria.fr/solverstack/vite/-/issues/22Installing with spack and OTF2 support: issue with default OTF2 version (3.0)2023-06-28T16:26:38+02:00Matthieu KuhnInstalling with spack and OTF2 support: issue with default OTF2 version (3.0)Hi,
It seems a more or less recent move of otf2 from version 2.3 to 3.0 broke the compilation of vite (branch master).
The interface has certainly changed, involving small updates into the OTF2 parser of vite (into src/parser/OTF2Parser...Hi,
It seems a more or less recent move of otf2 from version 2.3 to 3.0 broke the compilation of vite (branch master).
The interface has certainly changed, involving small updates into the OTF2 parser of vite (into src/parser/OTF2Parser/ParserDefinitionOTF2.hpp and/or src/parser/OTF2Parser/ParserDefinitionOTF2.cpp).
Please find spack error messages when trying to install vite with the default version of OTF2 which is now otf2@3.0 below.
Forcing installation with otf version 2.3 allows to install vite with spack (`spack install vite+otf2 ^otf2@2.3`).https://gitlab.inria.fr/solverstack/vite/-/issues/5doesn't show event values2020-10-21T18:25:35+02:00THIBAULT Samuelsamuel.thibault@inria.frdoesn't show event valuesHello,
In the attached paje trace, there are some event, but their value does not show up. For instance:
9 2571.417028000 prog_event 0_p gradient_reconstruction
(9 is PajeNewEvent)
This shows up as
Value: pro...Hello,
In the attached paje trace, there are some event, but their value does not show up. For instance:
9 2571.417028000 prog_event 0_p gradient_reconstruction
(9 is PajeNewEvent)
This shows up as
Value: program event type
Container: 0_program
Type: program event type
Date: 2571.42
i.e. only the name for the type of event (prog_event, named "program event type" earlier) is taken into account for both Type and Value, while I'd expect value to take the Value parameter of the PajeNewEvent line.
Samuel
[paje.trace](/uploads/1a09958e17987bc6c0454494854ab008/paje.trace)https://gitlab.inria.fr/solverstack/vite/-/issues/11Bad variable drawing2020-10-20T00:16:17+02:00THIBAULT Samuelsamuel.thibault@inria.frBad variable drawingHello,
Here is an example [paje.trace.zip](/uploads/a327b33662591889844d33d2ced68fb5/paje.trace.zip) of trace with bad-looking variable drawing.
If I really set to 0.0 the timing of all the first events until 0_w0's gf variable, I avoi...Hello,
Here is an example [paje.trace.zip](/uploads/a327b33662591889844d33d2ced68fb5/paje.trace.zip) of trace with bad-looking variable drawing.
If I really set to 0.0 the timing of all the first events until 0_w0's gf variable, I avoid the issue, but variables could show up on the fly during execution, so we would not have to do it, this drawing is really odd :)
Samuelhttps://gitlab.inria.fr/solverstack/vite/-/issues/17command-line svg export segfaults2020-10-19T22:23:26+02:00Antoine Jegocommand-line svg export segfaultsHello!
I have pajé traces I want to export to svg.
When opening my trace (`vite paje.trace`) then `Ctrl+E > "export.svg" > Save`, the export is fine.
However when I try to use the command-line interface (`vite paje.trace -e export.svg`...Hello!
I have pajé traces I want to export to svg.
When opening my trace (`vite paje.trace`) then `Ctrl+E > "export.svg" > Save`, the export is fine.
However when I try to use the command-line interface (`vite paje.trace -e export.svg`) it crashes with the following message
> export of paje.trace to export.svg between the beginning of the trace to the end of the trace.
>
> Loading of the trace : 100% ~ Parsing... Remaining: 0 s
>
> double free or corruption (out)
>
> Aborted (core dumped)
My version of vite is the following
> the Visual Trace Explorer - version 1.2 - July 2010
(I got vite through `sudo apt-get install vite`)
Antoinehttps://gitlab.inria.fr/solverstack/vite/-/issues/18svg export does not display states2020-10-19T21:32:17+02:00Johnny Jazeixsvg export does not display statesWhether it's command-line or via the menu, the svg export does not display states.Whether it's command-line or via the menu, the svg export does not display states.https://gitlab.inria.fr/solverstack/vite/-/issues/4crashes with big trace2020-04-27T17:40:17+02:00THIBAULT Samuelsamuel.thibault@inria.frcrashes with big traceI tried master with a big trace (I copied it to plafrim:\~thibault/paje.trace.big), and it crashes:
```
init
Version GLSL : 1.30
130
init ok
gui init
Core::draw_trace
[New Thread 0x7f935e356700 (LWP 5830)]
[New Thread 0x7f935db55700 (LW...I tried master with a big trace (I copied it to plafrim:\~thibault/paje.trace.big), and it crashes:
```
init
Version GLSL : 1.30
130
init ok
gui init
Core::draw_trace
[New Thread 0x7f935e356700 (LWP 5830)]
[New Thread 0x7f935db55700 (LWP 5831)]
[New Thread 0x7f935d354700 (LWP 5832)]
btLoading of the trace : 25% ~ Parsing... Remaining: 2 s
draw wait
draw wait
Loading of the trace : 54% ~ Parsing... Remaining: 1 s
Loading of the trace : 80% ~ Parsing... Remaining: 0 s
QThread: Destroyed while thread is still running
Thread 8 "QThread" received signal SIGABRT, Aborted.
[Switching to Thread 0x7f935e356700 (LWP 5830)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: Aucun fichier ou dossier de ce type.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007f937b77242a in __GI_abort () at abort.c:89
#2 0x00007f937c40c107 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
#3 QMessageLogger::fatal (this=this@entry=0x7f935e355660, msg=msg@entry=0x7f937c6eb898 "QThread: Destroyed while thread is still running") at global/qlogging.cpp:796
#4 0x00007f937c41b31d in QThread::~QThread (this=0x7f935e355790, __in_chrg=<optimized out>) at thread/qthread.cpp:429
#5 0x0000555555670e73 in mt_ParserPaje::parse (this=0x555556732bb0, trace=..., finish_trace_after_parse=<optimized out>) at ./src/parser/PajeParser/mt_ParserPaje.cpp:166
#6 0x00005555555ed2d9 in ParsingThread::run (this=0x7fffffffc9f0) at ./src/parser/ParsingThread.cpp:78
#7 0x000055555567a875 in ParsingThread::qt_static_metacall (_o=0x7fffffffc9f0, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./obj-x86_64-linux-gnu/src/vite_autogen/35XDVXVAUK/moc_ParsingThread.cpp:82
#8 0x00007f937c62e3d2 in QObject::event (this=0x7fffffffc9f0, e=<optimized out>) at kernel/qobject.cpp:1246
#9 0x00007f937d37946c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007f937d380d34 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f937c5fed68 in QCoreApplication::notifyInternal2 (receiver=0x7fffffffc9f0, event=event@entry=0x55555672fdd0) at kernel/qcoreapplication.cpp:1018
#12 0x00007f937c6014dd in QCoreApplication::sendEvent (event=0x55555672fdd0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
#13 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x555555c8bb20) at kernel/qcoreapplication.cpp:1678
#14 0x00007f937c601a68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1532
#15 0x00007f937c657dd3 in postEventSourceDispatch (s=0x7f93580012d0) at kernel/qeventdispatcher_glib.cpp:276
#16 0x00007f9377d18bf7 in g_main_dispatch (context=0x7f9358000990) at ../../../../glib/gmain.c:3148
#17 g_main_context_dispatch (context=context@entry=0x7f9358000990) at ../../../../glib/gmain.c:3813
#18 0x00007f9377d18e60 in g_main_context_iterate (context=context@entry=0x7f9358000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3886
#19 0x00007f9377d18f0c in g_main_context_iteration (context=0x7f9358000990, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3947
#20 0x00007f937c6573ff in QEventDispatcherGlib::processEvents (this=0x7f93580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#21 0x00007f937c5fcdba in QEventLoop::exec (this=this@entry=0x7f935e355e80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#22 0x00007f937c41c3ca in QThread::exec (this=<optimized out>) at thread/qthread.cpp:515
#23 0x00007f937c42129d in QThreadPrivate::start (arg=0x7fffffffc9d0) at thread/qthread_unix.cpp:368
#24 0x00007f9379303494 in start_thread (arg=0x7f935e356700) at pthread_create.c:333
#25 0x00007f937b826abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
(gdb)
```https://gitlab.inria.fr/solverstack/vite/-/issues/15build failure with designated initializers2018-12-06T13:10:05+01:00Ghost Userbuild failure with designated initializersMerci pour la vitesse avec Qt4!
Mais avec gcc7:
```
[ 76%] Building CXX object src/CMakeFiles/vite.dir/parser/OTF2Parser/ParserDefinitionOTF2.cpp.o
cd /builddir/build/BUILD/vite-297d71d28a55198a67faec1701532bdd48fb5e43/src && /opt/rh/de...Merci pour la vitesse avec Qt4!
Mais avec gcc7:
```
[ 76%] Building CXX object src/CMakeFiles/vite.dir/parser/OTF2Parser/ParserDefinitionOTF2.cpp.o
cd /builddir/build/BUILD/vite-297d71d28a55198a67faec1701532bdd48fb5e43/src && /opt/rh/devtoolset-7/root/usr/bin/c++ -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_UITOOLS_LIB -DQT_XML_LIB -DWITH_OTF2 -I/opt/rh/loveshack-profiling-backports/root/usr/include -I/builddir/build/BUILD/vite-297d71d28a55198a67faec1701532bdd48fb5e43/src/common -I/builddir/build/BUILD/vite-297d71d28a55198a67faec1701532bdd48fb5e43/src -I/builddir/build/BUILD/vite-297d71d28a55198a67faec1701532bdd48fb5e43/externals/qtcolorpicker/src -isystem /usr/include/QtOpenGL -isystem /usr/include/QtUiTools -isystem /usr/include/QtGui -isystem /usr/include/QtXml -isystem /usr/include/QtCore -std=gnu++14 -O2 -g -DNDEBUG -o CMakeFiles/vite.dir/parser/OTF2Parser/ParserDefinitionOTF2.cpp.o -c /builddir/build/BUILD/vite-297d71d28a55198a67faec1701532bdd48fb5e43/src/parser/OTF2Parser/ParserDefinitionOTF2.cpp
/builddir/build/BUILD/vite-297d71d28a55198a67faec1701532bdd48fb5e43/src/parser/OTF2Parser/ParserDefinitionOTF2.cpp: In static member function 'static OTF2_CallbackCode ParserDefinitionOTF2::handler_DefMetricClass(void*, OTF2_MetricRef, uint8_t, const OTF2_MetricMemberRef*, OTF2_MetricOccurrence, OTF2_RecorderKind)':
/builddir/build/BUILD/vite-297d71d28a55198a67faec1701532bdd48fb5e43/src/parser/OTF2Parser/ParserDefinitionOTF2.cpp:359:5: sorry, unimplemented: non-trivial designated initializers not supported
};
^
```
[J'ais seulement un petit peu de Français :-(]https://gitlab.inria.fr/solverstack/vite/-/issues/14Qt4 build failure2018-12-03T19:18:47+01:00Ghost UserQt4 build failureI'm trying to build the current development ViTE (f96665f) on centos7.
I can't use Qt5 as centos/fedora is missing QtUiTools, and the Qt4 build
fails with
```
/builddir/build/BUILD/vite-f96665f224ddb90657bc1f85da87e6ed14e2e3eb/src/com...I'm trying to build the current development ViTE (f96665f) on centos7.
I can't use Qt5 as centos/fedora is missing QtUiTools, and the Qt4 build
fails with
```
/builddir/build/BUILD/vite-f96665f224ddb90657bc1f85da87e6ed14e2e3eb/src/common/Session.cpp: In static member function 'static Palette* Session::get_palette(const string&, const string&)':
/builddir/build/BUILD/vite-f96665f224ddb90657bc1f85da87e6ed14e2e3eb/src/common/Session.cpp:310:63: error: 'class QMap<QString, QVariant>' has no member named 'cbegin'; did you mean 'begin'?
for(QMap<QString, QVariant>::const_iterator it = qmap.cbegin() ;
^~~~~~
/builddir/build/BUILD/vite-f96665f224ddb90657bc1f85da87e6ed14e2e3eb/src/common/Session.cpp:311:24: error: 'class QMap<QString, QVariant>' has no member named 'cend'; did you mean 'end'?
it != qmap.cend() ; ++ it) {
^~~~
make[2]: *** [src/CMakeFiles/vite.dir/common/Session.cpp.o] Error 1
```
I'm afraid I'm not sufficiently confident to try to fix it in a reasonable time, but it seems to have been broken by the OTF2 merge (which I want!).https://gitlab.inria.fr/solverstack/vite/-/issues/9Crashes on extended Event type definition2018-12-03T19:14:17+01:00THIBAULT Samuelsamuel.thibault@inria.frCrashes on extended Event type definitionHello,
It is allowed to set different types of events with different sets of values, for instance in the attached [paje.trace.zip](/uploads/af668b6927e60ea42b8629a493c1cb12/paje.trace.zip) , there is both a PajeNewEvent 9 with the stand...Hello,
It is allowed to set different types of events with different sets of values, for instance in the attached [paje.trace.zip](/uploads/af668b6927e60ea42b8629a493c1cb12/paje.trace.zip) , there is both a PajeNewEvent 9 with the standard values, and a PajeNewEvent 20 with more values. Currently vite sometimes crashes on opening such file (I mean, if I keep opening the file, vite crashes like one time every two).
SamuelMathieu FavergeMathieu Favergehttps://gitlab.inria.fr/solverstack/vite/-/issues/13clang, clazy, cppcheck application to use c++11 improvements2018-12-03T08:45:28+01:00Johnny Jazeixclang, clazy, cppcheck application to use c++11 improvementsHi,
as I can't do pull request, I open a bug to list a few patches I've done applying clang-tidy, clazy and cppcheck.
I didn't fix all the existing warnings/errors. I've separated in different patches to not have a too long diff.
[1-mod...Hi,
as I can't do pull request, I open a bug to list a few patches I've done applying clang-tidy, clazy and cppcheck.
I didn't fix all the existing warnings/errors. I've separated in different patches to not have a too long diff.
[1-modernize-nullptr.diff](/uploads/9505aaf698914dbc0648e71bc36136ed/1-modernize-nullptr.diff)
[2-modernize-use-equals-default.diff](/uploads/0972e72a67f27b5d61e2e067fb7013a8/2-modernize-use-equals-default.diff)
[3-modernize-use-default-member-init.diff](/uploads/a0840e418b90e0f7b25eca520d2aee67/3-modernize-use-default-member-init.diff)
[4-clazy-qvariant-template-instantiation.diff](/uploads/06467c1e4bf718e4a90398b3794463f5/4-clazy-qvariant-template-instantiation.diff)
[5-clazy-incorrect-emit.diff](/uploads/39ad084596ddae73bc3729bd9627dc35/5-clazy-incorrect-emit.diff)
[6-clang-performance.diff](/uploads/359d48b567ca716e2461529e2687c198/6-clang-performance.diff)
[7-gcc-partial-Wall.diff](/uploads/adc7d6caea449d936ff19bbdf1f03a38/7-gcc-partial-Wall.diff)
[8-modernize-use-override.diff](/uploads/1822ef8359e30d7295268c003d5c6907/8-modernize-use-override.diff)
[9-modernize-loop-convert.diff](/uploads/23e248354b1334df710c4c47bff99b9e/9-modernize-loop-convert.diff)
[99-fix-Distribution-plugin.diff](/uploads/219ff524f9a61bf90b3cb9d8b3f6510d/99-fix-Distribution-plugin.diff)
Johnnyhttps://gitlab.inria.fr/solverstack/vite/-/issues/12Compilation issue on Arch Linux2018-11-21T09:56:42+01:00François TrahayCompilation issue on Arch LinuxHi,
On Arch Linux, Vite fails to compile because some opengl features it use are now flags as "experimental":
> [ 81%] Building CXX object src/CMakeFiles/vite.dir/core/Core.cpp.o
> In file included from /var/lib/runner/build/vite-svn/s...Hi,
On Arch Linux, Vite fails to compile because some opengl features it use are now flags as "experimental":
> [ 81%] Building CXX object src/CMakeFiles/vite.dir/core/Core.cpp.o
> In file included from /var/lib/runner/build/vite-svn/src/vite-svn/src/render/Render_alternate.hpp:60,
> from /var/lib/runner/build/vite-svn/src/vite-svn/src/core/Core.cpp:121:
> /usr/include/glm/gtx/transform.hpp:23:3: error: #error "GLM: GLM_GTX_transform is an experimental extension and may change in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really want to use it."
> # error "GLM: GLM_GTX_transform is an experimental extension and may change in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really want to use it."
> ^~~~~
This can be fixed by adding a #define:
[glx_experimental.patch](/uploads/a005d931d6c395910a6970dd8af91e75/glx_experimental.patch)https://gitlab.inria.fr/solverstack/vite/-/issues/8fails to build with recent version of glm2018-03-02T17:37:28+01:00THIBAULT Samuelsamuel.thibault@inria.frfails to build with recent version of glmAs reported on http://bugs.debian.org/888795 , the new version of glm requires to #define GLM_ENABLE_EXPERIMENTAL to be able to include glm/gtx/transform.hpp, because its interface may change.As reported on http://bugs.debian.org/888795 , the new version of glm requires to #define GLM_ENABLE_EXPERIMENTAL to be able to include glm/gtx/transform.hpp, because its interface may change.https://gitlab.inria.fr/solverstack/vite/-/issues/3Crashes on color mangling2018-03-02T17:33:21+01:00THIBAULT Samuelsamuel.thibault@inria.frCrashes on color manglingHello,
I tried to tune the colors, and vite crashed. Opening for instance this file
[paje.trace](/uploads/1e1a79a58558268e728aaf86c891ded5/paje.trace)
tasks show up in green. I then go to Preferences->Settings, States tab, go down to ch...Hello,
I tried to tune the colors, and vite crashed. Opening for instance this file
[paje.trace](/uploads/1e1a79a58558268e728aaf86c891ded5/paje.trace)
tasks show up in green. I then go to Preferences->Settings, States tab, go down to chol_model_11, which show up as black instead of green (?!), and at the same time I get this warning in the console: "QColor::setRgb: RGB parameters out of range", I don't even change anything, and then vite crashes with "/build/vite-1.2+svn+git2.ea4d767/src/render/Render_alternate.cpp :94 : void checkGlError(): l'assertion « rc == GL_NO_ERROR » a échoué."
Samuelhttps://gitlab.inria.fr/solverstack/vite/-/issues/6Pb with limits when zoom in2018-03-01T18:32:55+01:00Mathieu FavergePb with limits when zoom inWhen the mouse goes outside the bow, the limits of the zoom are not limited to the min/max value of the window.When the mouse goes outside the bow, the limits of the zoom are not limited to the min/max value of the window.CHEVALIER ArthurCHEVALIER Arthurhttps://gitlab.inria.fr/solverstack/vite/-/issues/2compilation issues on MacOS2017-08-29T15:41:15+02:00RAMET Pierrecompilation issues on MacOS```
[ 19%] Building CXX object src/CMakeFiles/vite.dir/interface/Interval_select.cpp.o
/Users/ramet/Work/vite/src/interface/Interval_select.cpp:266:34: error:
non-constant-expression cannot be narrowed from type 'double' to
'...```
[ 19%] Building CXX object src/CMakeFiles/vite.dir/interface/Interval_select.cpp.o
/Users/ramet/Work/vite/src/interface/Interval_select.cpp:266:34: error:
non-constant-expression cannot be narrowed from type 'double' to
'Element_pos' (aka 'float') in initializer list [-Wc++11-narrowing]
Element_pos zoom[2]={minSpinBox->value(), maxSpinBox->value()};
^~~~~~~~~~~~~~~~~~~
/Users/ramet/Work/vite/src/interface/Interval_select.cpp:266:34: note: insert an
explicit cast to silence this issue
Element_pos zoom[2]={minSpinBox->value(), maxSpinBox->value()};
^~~~~~~~~~~~~~~~~~~
static_cast<Element_pos>( )
/Users/ramet/Work/vite/src/interface/Interval_select.cpp:266:55: error:
non-constant-expression cannot be narrowed from type 'double' to
'Element_pos' (aka 'float') in initializer list [-Wc++11-narrowing]
Element_pos zoom[2]={minSpinBox->value(), maxSpinBox->value()};
^~~~~~~~~~~~~~~~~~~
/Users/ramet/Work/vite/src/interface/Interval_select.cpp:266:55: note: insert an
explicit cast to silence this issue
...Element_pos zoom[2]={minSpinBox->value(), maxSpinBox->value()};
^~~~~~~~~~~~~~~~~~~
static_cast<Element_pos>( )
2 errors generated.
```