Activity for Wasilios Goutas
-
Wasilios Goutas posted a comment on discussion Help
Hi Eckard, sorry for the late reply. I'm quite bussy this days. I can't provide the the log and xml files you requested, as they contain confidential code. I will try to get an compiler installed on my machine to build the Moritz binaries and check where xml2abc is crashing. Best regards Wasili
-
well, after copying the LangPack folder to the working directory of the project, I of curse do not get the error message of the missing file idToCharacter.* but still get the crash
-
Hello Eckard, after downloading the patched binaries created on 23rd Dec and the latest SVN dump from 30th Dec I'm not able to generate any NSD any more. While abc2xml is running through the C sources and generates xml files, a call to xml2abc with an NSD configuration informs about the missing itToCharacter.xml and crashes load configuration-file added under configuration root called "Configuration" the new sub-node : <UserArgument> <LogRoot value=".\result\log"/> <RootPath value="A:\tools\Moritz\distribution\Moritz\Development\Moritz_Dev"/>...
-
Hello Eckard, after downloading the patched binaries created on 23rd Dec and the latest SVN dump from 30th Dec I'm not able to generate any NSD any more. While abc2xml is running through the C sources and generates xml files, a call to xml2abc with an NSD configuration informs about the missing itToCharacter.xml and crashes %MORITZ_PATH%\bin\xml2abc UA:LogRoot=%MORITZ_LOG_PATH% UA:RootPath=%MORITZ_PATH% UA:ResultPath=%MORITZ_RESULTS% CF.\cfg\ansi_c_xml2abc_cfg_nsd.xml > %MORITZ_LOG_PATH%\log_xml2abc_nsd.log...
-
Hello Eckard, after downloading the patched binaries created on 23rd Dec and the latest SVN dump from 30th Dec I'm not able to generate any NSD any more. While abc2xml is running through the C sources and generates xml files, a call to xml2abc with an NSD configuration informs about the missing itToCharacter.xml and stops. load configuration-file added under configuration root called "Configuration" the new sub-node : <UserArgument> <LogRoot value=".\result\log"/> <RootPath value="A:\tools\Moritz\distribution\Moritz\Development\Moritz_Dev"/>...
-
Hello Eckard, I downloaded the latest Moritz snapshot from 23rd Dec 20 and the patched binaries xml2abc Version 2.1.0 generation of nassi shneiderman diagrams for source-codes Copyright (C) 2004-2020 by Eckard Klotz Build date: Dec 23 2020 , time: 13:05:37 Build as : 64 bit application but when using this combination all files been processed by abc2xml create ..._c_code.xml files are 32Byte long and contain the same content <Content L="1" C="1"></Content> Even when making use of the old binaries...
-
Hello Eckard, I found a way to make use of the patch from 23rd Dec. 20. The reproducer is working with the new binaries and the configuration files you provided. Unfortunately the output of the sources I'm working on is behaving different. I tested the changes with both binary versions (the one from 10th June and the new one of 23.Dec) and the results I get now is, that all sources of my source tree result in xml files called ...filename...c_code.xml contain nothing but the following <Content L="1"...
-
assembler support
-
int16_t not supported (but uint16_t is)
-
brackets confusing the parser
-
reproduser attached
-
#if ( ... ) fails
-
reproduser attached
-
struct initializer with condition
-
Thanks Eckard, I tested it and it works BR Wasili
-
Thanks Eckard, I tested it and it works
-
Hello Eckard, on my system is a mixture of Moritz binaries from June 2020 and configuration files from the SVN repository from November I think. Maybe the behavior on my system is caused by this. If on your system it is working as expected than its fine. I don't need this functionality by now. BR Wasili
-
initializing array failed
-
#if 1 not supported
-
abc2xml configured to parse single file failes on include statement
-
Hello Eckard, many thanks for being that fast in providing the fix. Unfortunately I can't download executables and will need to wait until you created a new release containing this fix to get it provided by the companies IT department. As I have a workaround, it is not a blocker for me to continue using Moritz :) Wish you merry Christmas and a happy new year Wasili
-
xml2abc concats paths to create logfiles -- fails with absolut paths
-
Hello Eckard, thanks a lot. Unfortunately I'm not able to download archives including executables and have not an compiler available on the machine I'm using Moritz. I will try to get someone of my team compile the sources ... As I'm not blocked by this, it might take some time till I will be able to make use of your latest changes BR Wasili
-
I corrected my script to make use of the LogPath in all 3 calls %MORITZ_PATH%\bin\abc2xml UA:LogRoot=%MORITZ_LOG_PATH% UA:RootPath=%MORITZ_PATH% CF.\cfg\ansi_c_abc2xml_cfg.xml > %MORITZ_LOG_PATH%\log_abc2xml.txt %MORITZ_PATH%\bin\xml2abc UA:LogRoot=%MORITZ_LOG_PATH% UA:RootPath=%MORITZ_PATH% CF.\cfg\ansi_c_xml2abc_cfg_nsd.xml > %MORITZ_LOG_PATH%\log_xml2abc_nsd.txt %MORITZ_PATH%\bin\xml2abc UA:LogRoot=%MORITZ_LOG_PATH% UA:RootPath=%MORITZ_PATH% CF.\cfg\ansi_c_xml2abc_cfg_uad.xml > %MORITZ_LOG_PATH%\log_xml2abc_uad.txt...
-
Hello Eckard, I tried it by using command line parameter like this %MORITZ_PATH%\bin\abc2xml UA:LogRoot=%MORITZ_LOG_PATH% UA:RootPath=%MORITZ_PATH% CF.\cfg\ansi_c_abc2xml_cfg.xml > %MORITZ_LOG_PATH%\log_abc2xml.txt and it created the LangPack folder where I configured it to be. Unfortuntely I still get a LangPack and xml folder in the working directory which does not contain any files (tree used from Cygwin) $ tree . ├── 0_create.bat ├── 1_create_Prb.bat ├── 2_create_Msc.bat ├── cfg │ ├── ansi_c_abc2xml_cfg.xml...
-
Hello Eckard, I tried it by using command line parameter like this %MORITZ_PATH%\bin\abc2xml UA:LogRoot=%MORITZ_LOG_PATH% UA:RootPath=%MORITZ_PATH% CF.\cfg\ansi_c_abc2xml_cfg.xml > %MORITZ_LOG_PATH%\log_abc2xml.txt and it created the LangPack folder where I configured it to be. Unfortuntely I still get a LangPack and xml folder in the working directory which does not contain any files (tree used from Cygwin) $ tree . ├── 0_create.bat ├── 1_create_Prb.bat ├── 2_create_Msc.bat ├── cfg │ ├── ansi_c_abc2xml_cfg.xml...
-
thanks Eckard, I will try it soon BR Wasili
-
Hello, I realized, that when runnining the motitz toolset, the working directory in which I started the script contains additional folders with logfiles. In detail these are LangPack/ansi_c/_log/grm/ and xml/log/ Is there a way to configure the abc2xml and xml2abc tools to create this folders somewhere else? I would like to keep the source dir which inlcudes the moritz configurations and scripts clean. BR Wasili
-
Hello Eckard, the solution of defining the longer name first works. The way you mentioned by the '-' (minus operator) I haven't tested as I do not understand it, and it seems not needed for what I'm trying. Thanks Wasili
-
HI Eckard, I double checked it with the version on my disc and you are right. I have defined the leading string with 2 underscores. I just re-ran the test and the result is the same, the function test4 with 2 different preprocessor directives in the parameter list still fails. ("__" >> "FUNC_RET_PREPROCESSOR") | ("__" >> "FUNC_PARAM_PREPROCESSOR") | ("__" >> "FUNC_PARAM_PREPROCESSOR_NEW") I will check the discussion forum and provide feedback. BR Wasili
-
Hello Eckard, ok, build and run make sense. Sorry to not have read the docs so far in detail. BR Wasili
-
Hi Eckard, sorry for being so precise. I tried today to get the latest version and start the examples/tutorials from scratch. I have on my desk the latest sources, etc. being part of the SVN archive https://sourceforge.net/projects/moritz/files/Moritz_2.x/DevelopmentFor_2_1_0/TemporaryFolder/Archiev_SVN_2020_11_28.zip/download Unfortunately I do not have an compiler installed on the machine where I try to make use of Moritz, so I copied the binaries I had, based on the installation the IT provided...
-
Hi, I try to run the MessageSequence_1 example but I'm failing. I'm using even the examples from the latest SVN snapshot as the examples I had before provided such message: warning: you are using an old configuration file! ->Please rename in your user-configuration the last tag, used to include the process-configuration, from "GeneratorNSD" into "Process" using the latest snapshot example provides me You are already using a new and valid configuration to include the process-configuration. -> There...
-
Hi, I try to run the MessageSequence_1 example but I'm failing. I'm using even the examples from the latest SVN snapshot as the examples I had before provided such message: warning: you are using an old configuration file! ->Please rename in your user-configuration the last tag, used to include the process-configuration, from "GeneratorNSD" into "Process" using the latest snapshot example provides me You are already using a new and valid configuration to include the process-configuration. -> There...
-
different user grammars in function parameter list
-
It seems I need to reopen this issue :( unfortunately it seems not possible to me :). I hope this update will reach you When making use of 2 different user defined grammars in a function parameter list it is not working. See function static __FUNC_RET_PREPROCESSOR myUnnamedBitFields_t test4( __FUNC_PARAM_PREPROCESSOR const myUnnamedBitFields_t param1, __FUNC_PARAM_PREPROCESSOR_NEW myUnnamedBitFields_t param2 ); The user grammar I use contains this | ("" >> "FUNC_RET_PREPROCESSOR") | ("" >> "FUNC_PARAM_PREPROCESSOR")...
-
It seems I need to reopen this issue :( When making use of 2 different user defined grammars in a function parameter list it is not working. See function static __FUNC_RET_PREPROCESSOR myUnnamedBitFields_t test4( __FUNC_PARAM_PREPROCESSOR const myUnnamedBitFields_t param1, __FUNC_PARAM_PREPROCESSOR_NEW myUnnamedBitFields_t param2 ); The user grammar I use contains this | ("" >> "FUNC_RET_PREPROCESSOR") | ("" >> "FUNC_PARAM_PREPROCESSOR") | ("__" >> "FUNC_PARAM_PREPROCESSOR_NEW") The code attached,...
-
Hello Eckard, thanks for the user grammar update. I will test it soon. Regarding the C standard compliance I meant that the code after the not complaint part. The wish is a fail tolerant parser, just ignoring the code parts not been syntactical correct, but I understand if this is not possible, as such parser is quite complicated and not stateless. BR Wasili
-
Hi, I identified, that Moritz is following the rule to continue processing source trees even a file contains a syntax error. What I mean is, when a couple of sources are given, and one of them violates the language syntax been supported, the file is not been analyzed further but the rest of the file is skipped, and Moritz proceeds with the remaining files. That's fine, but I would like to ask if this behavior is configurable and I will be able to force Moritz to proceed with the file containing syntax...
-
Hi, I identified, that Moritz is following the rule to continue processing source trees even a file contains a syntax error. What I mean is, when a couple of sources are given, and one of them violates the language syntax been supported, the file is not been analyzed further but the rest of the file is skipped, and Moritz proceeds with the remaining files. That's fine, but I would like to ask if this behavior is configurable and I will be able to force Moritz to proceed with the file containing syntax...
-
Hello Eckard, the results I have seen so far looks good. Thanks for the fix :) BR Wasili
-
Thanks you Eckard, I will test it and give feedback
-
Thanks you Eckard, I will test it and give fedback
-
Unfortunately I'm not able to get positive results when having a user grammar followed by a const. I expect it never worked so far and I was just wrong in my statement earlier. My grammar meanwhile looks as follows: userAttribute = ("" >> "VARIABLE_PREPROCESSOR") | ("" >> "FUNC_RET_PREPROCESSOR") | ("" >> "FUNC_PARAM_PREPROCESSOR") | ("" >> "FUNC_PARAM_PREPROCESSOR" >> " const") | ("__" >> "FUNC_PARAM_PREPROCESSOR" >> *" " >> "const") ; and the code I'm testing it with is this: static __FUNC_RET_PREPROCESSOR...
-
the strange thing is, that meanwhile the 'const' expression is not working an more. I think I need to start reviewing my changes to identify why it worked earlier today.
-
Hello Eckard, thank you for providing the possibility for user grammar, and sorry for answering tht late. Meanwhile I was able to run first tests. I merged the changes of the above files to the changes you provided based on the issues #9 unnamed fields in struct/union not handled I realized, that the user grammar been added in the file UserGrammar.a2x is also part of the file ANSI_C_Source_C_only_grm.a2x. I expect that this had been added while doing the proof of concept and forgotten to be removed....
-
I will try soon, thanks
-
Hi Eckard, it seems to work partly. It works when making use of int, float but not when I use structures as return values or parameters to functions like this: typedef struct { int a; } aStruct_t; static __FUNC_RET_PREPROCESSOR aStruct_t test1( __FUNC_PARAM_PREPROCESSOR aStruct_t param1 ){ int ret; return ret; }
-
maybe there is a way to configure the Moritz log files LangPack - ansi_c - _log _ grm xml - log to be stored at a different folder. This would enable to get them out of the source tree so Doxygen will not find them
-
dotfile collections and file endings
-
issue can be closed :)
-
preprocessor directive issue
-
Thanks a lot. A quick check showed that in the project I'm using Moritz some nsd files more have been generated. Will try to check it in detail tomorrow. BR Wasili
-
Thanks a lot. A quick check showed that in the project I'm using Moritz some nsd files more have geen generated. Will try to check it in detail tomorrow. BR Wasili
-
unnamed fields in struct/union not handled
-
Hello Eckard, thanks this fixed the issue. Do I understand it correct, that the C, C++, etc syntax scanner is been implemented by your tools based on the grammar configured in the a2x folder? Seem quite challenging to be adapted when a new standard is been published. Since there is no C/C++ compiler involved, is Moritz able to handle compiler switches? I'm asking since the most code If seen makes heavy use use of #ifdef statements to differentiate versions etc. BR Wasili
-
Hello Eckard, I have identified, that a special C syntax is not supported and breaks any processing of Moritz without any information (at least I haven't found any). When making use of 'designated initializer' as part of a function parameter list, the function in which this is been used and all following in the same source file are missing in the NSD & DOT outputs. With the attached C code is is reproducible what I mean. I expect the C parser is part of a LanguagePack grammar definition, but I do...
-
Hello Eckard, in the 'Introduction.pdf' on the last paragraph on page #20 you mentioned it is possible to support software tests by adding stub-modules ... Do you have an example on how you managed to do so? BR Wasili
-
Hello Eckard, can I prevent the tools from creating Langpack and xml logs in the working directory? BR Wasili
-
Hello Eckhard, can I prevent the tools from creating Langpack and xml logs in the working directory? BR Wasili
-
Hello again, I noticed that you provide Linux executable but these are build for Arm Linux only. Do you plan to release also x86 Linux 64bit versions in future? I build the binaries out of the sources and needed to rename one File to have thge first character in upper case if I remember corretly, unfortunately I forgot which it was (I think something like Utils*.h) BR Wasili
-
Hello Eckahrd, in the 'Introduction.pdf' on the last paragraph on page #20 you mentioned it is possible to support software tests by adding stub-modules ... Do you have an example on how you managed to do so? BR Wasili
-
Hello Eckhard, I have identified, that a special C syntax is not supported and breaks any processing of Moritz without any information (at least I haven't found any). When making use of 'designated initializer' as part of a function parameter list, the function in which this is been used and all following in the same source file are missing in the NSD & DOT outputs. With the attached C code is is reproducible what I mean. I expect the C parser is part of a LanguagePack grammar definition, but I do...
1