Feature Req: parsing output of build script

In Eclipse, you can parse the output of the build command, parsing for file names / string #s, so each error/warning output line could be used to navigate straight to the source code location. Extremely handy.

For example, should my unit test core dump, my build script runs gdb on it - to output the stack trace and that is then fed into eclipse, so I can instantly jump to source code locations. Extremely handy.

3 comments
Comment actions Permalink

CLion detects file paths in the output and allows to navigate to them if they belong to the current project. Please let me know if it does not work as expected for you.

http://take.ms/mmW2s

0
Comment actions Permalink

It certainly does that. But having ability to parse arbitrary output, via regex, to get to file name and line number, would be great to have.

Just a suggestion. Eclipse has it and I find it very handy.

For example, I frequently use "markers" - just a simple macro that spits out __FILE__ and __LINE__, along say with a var value. It helps to be able to click on the output line to just to that code location. Another example has me invoke gdb to produce a stack trace from a core file - again, letting you to jump around code.

0
Comment actions Permalink

All you need to do is to print your output in the same format: <full_path>:<line number>, and CLion will pick it up.

0

Please sign in to leave a comment.