From: Martin Quinson Date: Thu, 19 May 2016 18:23:01 +0000 (+0200) Subject: FAQ: kill a painfully outdated Q&A X-Git-Tag: v3_14~1203 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/5e6e83f7f7eca86f31dff4b95573af94781a68f7?hp=a01a7e62056a8ca98b42a0c5c91d0eb84c28c2ef FAQ: kill a painfully outdated Q&A --- diff --git a/doc/doxygen/FAQ.doc b/doc/doxygen/FAQ.doc index 44e4f9aaa7..2a8a74dae0 100644 --- a/doc/doxygen/FAQ.doc +++ b/doc/doxygen/FAQ.doc @@ -496,53 +496,6 @@ come after -lsimgrid on this command line. \subsection faq_trouble_errors Runtime error messages -\subsubsection faq_flexml_limit "surf_parse_lex: Assertion `next limit' failed." - -This is because your platform file is too big for the parser. - -Actually, the message comes directly from FleXML, the technology on top of -which the parser is built. FleXML has the bad idea of fetching the whole -document in memory before parsing it. And moreover, the memory buffer size -must be determined at compilation time. - -We use a value which seems big enough for our need without bloating the -simulators footprints. But of course your mileage may vary. In this case, -just edit src/surf/surfxml.l modify the definition of -FLEXML_BUFFERSTACKSIZE. E.g. - -\verbatim -#define FLEXML_BUFFERSTACKSIZE 1000000000 -\endverbatim - -Then recompile and everything should be fine, provided that your version of -Flex is recent enough (>= 2.5.31). If not the compilation process should -warn you. - -A while ago, we worked on FleXML to reduce a bit its memory consumption, but -these issues remain. There is two things we should do: - - - use a dynamic buffer instead of a static one so that the only limit - becomes your memory, not a stupid constant fixed at compilation time - (maybe not so difficult). - - change the parser so that it does not need to get the whole file in - memory before parsing - (seems quite difficult, but I'm a complete newbe wrt flex stuff). - -These are changes to FleXML itself, not SimGrid. But since we kinda hijacked -the development of FleXML, I can grant you that any patches would be really -welcome and quickly integrated. - -Update: A new version of FleXML (1.7) was released. Most of the work -was done by William Dowling, who use it in his own work. The good point is -that it now use a dynamic buffer, and that the memory usage was greatly -improved. The downside is that William also changed some things internally, -and it breaks the hack we devised to bypass the parser, as explained in -\ref pf_flexml_bypassing. Indeed, this is not a classical usage of the -parser, and Will didn't imagine that we may have used (and even documented) -such a crude usage of FleXML. So, we now have to repair the bypassing -functionality to use the latest FleXML version and fix the memory usage in -SimGrid. - \subsubsection faq_trouble_errors_big_fat_warning I'm told that my XML files are too old. The format of the XML platform description files is sometimes @@ -553,9 +506,9 @@ descriptions to allow more compact descriptions. That is why the XML files are versionned using the 'version' attribute of the root tag. Currently, it should read: -\verbatim - -\endverbatim +@verbatim + +@endverbatim If your files are too old, you can use the simgrid_update_xml.pl script which can be found in the tools directory of the archive.