TTool merge requestshttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests2021-01-18T15:27:58Zhttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/385Remarks update2021-01-18T15:27:58ZMaysam ZoorRemarks updatehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/384Remarks update2021-01-14T15:02:04ZMaysam ZoorRemarks updatehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/383Fix multicore double click and mulicore hanging2021-01-14T14:16:48ZLe Van TruongFix multicore double click and mulicore hangingLudovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/382Remarks update2021-01-13T17:51:03ZMaysam ZoorRemarks updatehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/381Remarks update2021-01-11T14:23:04ZMaysam ZoorRemarks updatehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/380Un-comment tests and add timeout for the tests2021-01-07T08:52:02ZLe Van TruongUn-comment tests and add timeout for the testsLudovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/379Un-comment tests and add timeout for the tests2021-01-06T21:59:34ZLe Van TruongUn-comment tests and add timeout for the testsLudovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/378add files2020-12-18T07:57:57ZMaysam Zooradd fileshttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/377commit MainGUI2020-12-16T15:20:08ZMaysam Zoorcommit MainGUIhttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/376Revert "Merge branch 'taintBranch' into 'master'"2020-12-16T10:50:41ZLudovic ApvrilleRevert "Merge branch 'taintBranch' into 'master'"This reverts merge request !375This reverts merge request !375https://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/375Taint branch2020-12-16T10:50:21ZMaysam ZoorTaint branchhttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/374Taint branch2020-12-15T09:13:03ZMaysam ZoorTaint branchhttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/373Draw vertical line for timeline diagram2020-12-10T14:32:05ZLe Van TruongDraw vertical line for timeline diagramLudovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/372Draw vertical line for timeline diagram2020-12-10T12:29:16ZLe Van TruongDraw vertical line for timeline diagramLudovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/371Fix memory leak and add test2020-11-26T14:43:28ZLe Van TruongFix memory leak and add testI have just fixed the memory leak problems showed by valgrind. Here are some notes:
* To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
* Two mains issues detected by valgrind were:
* *"definitel...I have just fixed the memory leak problems showed by valgrind. Here are some notes:
* To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
* Two mains issues detected by valgrind were:
* *"definitely lost"*: due to not freed variables.
* *"Conditional jump or move depends on uninitialised value(s)"*: due to not initialed variables.
* I have already find all possible variables that can lead to the *"definitely lost"* and freed it, and I also assigned the initial value to the variables which need it.
* Now your "DSD.xml" can run without error detected by valgrind. I have also run valgrind with a lot of models to make sure no more memory leak issues could happen. After this merge, if your problem still occur I guess the main issue come from the size of memory chunk for transaction allocation (it is now 8000000 bytes \~= 8 Mbs for each transaction).
* The test has two executed ways: with and without valgrind.Ludovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/370Revert "Merge branch 'revert-883077ef' into 'master'"2020-11-26T11:32:03ZLudovic ApvrilleRevert "Merge branch 'revert-883077ef' into 'master'"This reverts merge request !369This reverts merge request !369https://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/369Fix memory leak problem2020-11-26T11:20:59ZLe Van TruongFix memory leak problemI have just fixed the memory leak problems showed by valgrind. Here are some notes:
* To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
* Two mains issues detected by valgrind were:
* *"definitel...I have just fixed the memory leak problems showed by valgrind. Here are some notes:
* To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
* Two mains issues detected by valgrind were:
* *"definitely lost"*: due to not freed variables.
* *"Conditional jump or move depends on uninitialised value(s)"*: due to not initialed variables.
* I have already find all possible variables that can lead to the *"definitely lost"* and freed it, and I also assigned the initial value to the variables which need it.
* Now your "DSD.xml" can run without error detected by valgrind. I have also run valgrind with a lot of models to make sure no more memory leak issues could happen. After this merge, if your problem still occur I guess the main issue come from the size of memory chunk for transaction allocation (it is now 8000000 bytes \~= 8 Mbs for each transaction).
* The test has two executed ways: with and without valgrind.Ludovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/368Fix memory leak problem2020-11-26T10:29:47ZLe Van TruongFix memory leak problemI have just fixed the memory leak problems showed by valgrind. Here are some notes:
* To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
* Two mains issues detected by valgrind were:
* *"definitel...I have just fixed the memory leak problems showed by valgrind. Here are some notes:
* To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
* Two mains issues detected by valgrind were:
* *"definitely lost"*: due to not freed variables.
* *"Conditional jump or move depends on uninitialised value(s)"*: due to not initialed variables.
* I have already find all possible variables that can lead to the *"definitely lost"* and freed it, and I also assigned the initial value to the variables which need it.
* Now your "DSD.xml" can run without error detected by valgrind. I have also run valgrind with a lot of models to make sure no more memory leak issues could happen. After this merge, if your problem still occur I guess the main issue come from the size of memory chunk for transaction allocation (it is now 8000000 bytes \~= 8 Mbs for each transaction).
* The test has two executed ways: with and without valgrind.Ludovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/367Fix memory leak problem2020-11-25T22:56:24ZLe Van TruongFix memory leak problemI have just fixed the memory leak problems showed by valgrind. Here are some notes:
* To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
* Two mains issues detected by valgrind were:
* *"definitel...I have just fixed the memory leak problems showed by valgrind. Here are some notes:
* To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
* Two mains issues detected by valgrind were:
* *"definitely lost"*: due to not freed variables.
* *"Conditional jump or move depends on uninitialised value(s)"*: due to not initialed variables.
* I have already find all possible variables that can lead to the *"definitely lost"* and freed it, and I also assigned the initial value to the variables which need it.
* Now your "DSD.xml" can run without error detected by valgrind. I have also run valgrind with a lot of models to make sure no more memory leak issues could happen. After this merge, if your problem still occur I guess the main issue come from the size of memory chunk for transaction allocation (it is now 8000000 bytes \~= 8 Mbs for each transaction).
* The test has two executed ways: with and without valgrind.Ludovic ApvrilleLudovic Apvrillehttps://gitlab.telecom-paris.fr/mbe-tools/TTool/-/merge_requests/366Fix memory leak problem2020-11-23T13:19:16ZLe Van TruongFix memory leak problemI have just fixed the memory leak problems showed by valgrind. Here are some notes:
- To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
- Two mains issues detected by valgrind were:
- _"defini...I have just fixed the memory leak problems showed by valgrind. Here are some notes:
- To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
- Two mains issues detected by valgrind were:
- _"definitely lost"_: due to not freed variables.
- _"Conditional jump or move depends on uninitialised value(s)"_: due to not initialed variables.
- I have already find all possible variables that can lead to the _"definitely lost"_ and freed it, and I also assigned the initial value to the variables which need it.
- Now your "DSD.xml" can run without error detected by valgrind. I have also run valgrind with a lot of models to make sure no more memory leak issues could happen. After this merge, if your problem still occur I guess the main issue come from the size of memory chunk for transaction allocation (it is now 8000000 bytes ~= 8 Mbs for each transaction).Ludovic ApvrilleLudovic Apvrille