Author Topic: Configure Error Parsing...cannot get output to be recognised as an error  (Read 792 times)

vandermyer

  • Community Member
  • Posts: 47
  • Hero Points: 2
Hi All,

I wonder if anyone can help on this. I have successfully configured error parsing for my compiler, with errors displayed in the build window with a red cross in the left margin. I can click on the error lines in the build window and SE takes me to the error line. The Classification used for expressions is <Auto>, and the parsed lines have the word Error or Warning in them.

Having now configured error parsing for another tool, I cannot get lines that are successfully parsed to be recognized as errors or warnings, with the net result when I click on the output line SE brings up a 'Find File' dialog. The parsed output lines do not contain the words Warning or Error, so I set the Classification to Error expecting that this would trigger the red cross indication in the left margin. Parsing works successfully using the Validation button in the Edit Expression dialog for error parsing. How do i get these successfully parsed messages to be recognized as Errors?

I would post an image here of the successful parsing, but I can't seem to paste an image in and the 'Attachments and other options' doesn't has an attach option (that I can see). But I can say the parsing correctly matches filename, line, column and message.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 7133
  • Hero Points: 544
Try restarting but I don't think that will help. I'm guessing the filename can't be found because it is missing path information or it has a relative path but not to the current directory. If this isn't the case, email your user.cfg.xml to support and include a text file with compiler error output that matches the problematic error messages.