Opened 9 years ago

Closed 9 years ago

#3181 closed defect (fixed)

Compiler debug trace does not work (see first example of Users Guide)

Reported by: rfranke Owned by: adrpo
Priority: high Milestone: 1.9.2
Component: Frontend Version: trunk
Keywords: Cc:

Description

A debug trace would give some background info if flattening fails (see a couple of open tickets addressing the Frontend). Also the brand new OpenModelica Users Guide from Feb 2015 starts its first example session in section 1.2.2 with:

>> setDebugFlags("failtrace")
>> model A Integer t = 1.5; end A;
>> instantiateModel(A)

Unfortunately OpenModelica (r24785) just prints the regular error message without any stack trace. What happened to "failtrace"?

Change History (11)

comment:1 Changed 9 years ago by adrpo

You would need to add +showErrorMessages

comment:2 Changed 9 years ago by rfranke

Thanks!

comment:3 Changed 9 years ago by anonymous

I think that a list of all the flags (such as this +showErrorMessages) along with their meaning in the OM Users guide would be very useful. For instance it could be the last chapter or an appendix.
Not only OM users could find more easily how to do things that can be done with flags, but also this would reduce the time spent by developers in the Modelica Forum in answering questions whose answer invoves fags.

comment:4 Changed 9 years ago by rfranke

Most likely I had not found the flag in the last chapter or an appendix - I had tried a couple of different flags from the online help without success. I would just expect that the first introductory example session of the users manual works out of the box, i.e. that additionally required flags are mentioned there.

comment:5 Changed 9 years ago by rfranke

I'd love to add the hint to +showErrorMessage to the documentation and close the ticket. It's good to have OpenModelicaUsersGuide in the repository. But it's a doc blob!? Would it be thinkable to change to some readable format, like Markdown or Latex, so that additions become visible in the svn diff like source code changes?

comment:6 Changed 9 years ago by sjoelund.se

I have been complaining about the blob for years. I usually do not have Windows computers nearby so I even have to ask other people to change the file.
With latex, the pdf also would not need to be checked into svn since it could simply be re-compiled by the build process.

comment:7 Changed 9 years ago by adrpo

After we do the release I will translate it to latex (I do have a translator that we can use plus some manual editing).

comment:8 Changed 9 years ago by adrpo

Fixed in r24954 by removing the debug flags setting from the OMShell sessions as the debug flags are for developers and very advanced users only. Added section 1.4 with command line parameters and how to get more information from the compiler.

comment:9 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.2 to 1.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:10 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.3 to 1.9.2
  • Owner changed from somebody to adrpo
  • Status changed from new to assigned

comment:11 Changed 9 years ago by sjoelund.se

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.