Eclipse Community Forums: C / C++ IDE (CDT) » use own error parser under dosn't work under Linux

Home » Language IDEs » C / C++ IDE (CDT) » use own error parser under dosn't work under Linux(error parser)

use own error parser under dosn't work under Linux [message #1859327]

Wed, 31 May 2023 06:26

Eclipse User

Hello,

I've write my own error parser in Eclipse under Windows. Now I move this setting to Linux, but the error parser dosn't work correct.

In the Problems view are display the project name as resources and the path is empty.
Under windows it works correct. In the resources I see the file name and in the path the directory path started from the workspace.

Where comes this problem and how can I solve it?

Thanks for our help,
Bernd

Re: use own error parser under dosn't work under Linux [message #1859335 is a reply to message #1859327]

Wed, 31 May 2023 11:02

Eclipse User

In my experience, it's usually about tweaking the file path references in your parser code to align with the Linux directory structure. A key difference is that Linux uses forward slashes ("/") instead of the backslashes ("\") that Windows uses. So it's worth checking out if this is causing the problem.

Re: use own error parser under dosn't work under Linux [message #1859345 is a reply to message #1859335]

Thu, 01 June 2023 06:33

Eclipse User

The console output is (only one excample):
modules/csp-l/src/csp_l_nwk.c 181 note 9058: tag '_wakeup_mode_e' unused outside of typedefs [MISRA 2012 Rule 2.4, advisory]

The Problems view shows only the following informations for this message:
Description: tag '_wakeup_mode_e' unused outside of typedefs [MISRA 2012 Rule 2.4, advisory]
Resource: project_name
Path:
Location: line 181
Type: C/C++ Problem

The parser configuration is:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<plugin>
<extension id="PC-lint Plus Error Parser" name="PC-lint Plus Error Parser" point="org.eclipse.cdt.core.ErrorParser">
<errorparser class="org.eclipse.cdt.core.errorparsers.RegexErrorParser" id="org.eclipse.cdt.ui.PC-lint Plus Error Parser" name="PC-lint Plus Error Parser">
<pattern description-expr="$5" eat-processed-line="true" file-expr="$1" line-expr="$2" regex="(.*) (\d+)(\ +)info (\d+): (.*)" severity="Info"/>
<pattern description-expr="$5" eat-processed-line="true" file-expr="$1" line-expr="$2" regex="(.*) (\d+)(\ +)warning (\d+): (.*)" severity="Warning"/>
<pattern description-expr="$5" eat-processed-line="true" file-expr="$1" line-expr="$2" regex="(.*) (\d+)(\ +)note (\d+): (.*)" severity="Info"/>
<pattern description-expr="$5" eat-processed-line="true" file-expr="$1" line-expr="$2" regex="(.*) (\d+)(\ +)error (\d+): (.*)" severity="Error"/>
</errorparser>
</extension>
</plugin>

I think all is correct. The Windows tool give me the same message, the format is allways linux like :)

Previous Topic:	Find struct variable in C/C++ search
Next Topic:	Parallel build make not working as expected

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Nov 07 17:49:39 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter