MiSt

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • MiSt
    Participant

    Thank you for the link, this helped a lot. Unfortunately the data in the Output tab does not seem to be the raw error but something at is formated differently at least by my VS2013 version . Is there any way to turn this off?

    The error lay in the regex, the following worked for me (Arm Compiler 5.06u1):
    ^”([^:]+)”, line ([0-9]+): (Error|Warning):(.*)$
    This differs from the tutorial supplied file only that it does not expect a “:” character in the file location, and the compiler message contained relative paths.

    • This reply was modified 8 years, 7 months ago by MiSt.
    MiSt
    Participant

    I have verified that the file is located in  C:\Program Files (x86)\Sysprogs\VisualGDB . In the Properties of the Files it was blocked by Security, ich have clicked the unblock button and it doesn’t show up in the Properties anymore, but no change in behavior.

    What i have also seen is that in the Output tab a typical error message looks like “filepath”, line X : error : #X: description. The <GccMessage> entry has “(Error|Warning)” with capital E and the GCCDetailedMessage does not seem to fit. Might that be a problem (Although i know that in the direct compiler output Error is written with capital E, i don’t know which output gets parsed)?

Viewing 2 posts - 1 through 2 (of 2 total)