# 'Problems' view empty after build failure

**URL:** <https://forum.sierrawireless.com/t/problems-view-empty-after-build-failure/5122>\
**Category:** Development tools\
**Created:** [July 1, 2011, 2:49pm UTC](https://forum.sierrawireless.com/t/problems-view-empty-after-build-failure/5122 "2011-07-01T14:49:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [July 1, 2011, 2:49pm UTC](https://forum.sierrawireless.com/t/problems-view-empty-after-build-failure/5122/1 "2011-07-01T14:49:02Z")

</div>

A build just completed, with nothing at all shown in the ‘Problems’ view.

Rather naively, I took this to mean that there were no problems, and tried to download - DS told me that the image was already on the device.

So I looked at the Console view, and it showed that the build had, in fact, failed:

> [@](#):
>
> arm-elf-g++.exe: C:\OpenAT\SW\_Suite\_234\Embedded Software\com.wavecom.openat.ide.spm.lib.plugin.model.C-GPS-OPUS-I.1.7.0.2010\_1.7.0.2010\resources\C-GPS-OPUS-I\gcc\_CGPS\_0.0.0.5.1.libM-Wl,-): No such file or directory  
> Build error occurred, build is stopped  
> Time consumed: 16938 ms.

It would be really useful if the ‘Problems’ view gave a positive indication of when a build completes without problems!

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [July 4, 2011, 6:31am UTC](https://forum.sierrawireless.com/t/problems-view-empty-after-build-failure/5122/2 "2011-07-04T06:31:32Z")

</div>

OK, noticed for this one.  
Problems view is populated thanks to error parsers, which are probably not perfect… However you can enhance them by adding regular expressions allowing to catch errors which are not caught by the default integrated ones.  
Just go to: Window \> Preferences \> C/C++ \> Build  
In the Error Parsers list, select the one you’re interested (e.g. here the Link error parser for ARM/MinGW GCC), and from there you can customize the regular expressions.

However, we’ll integrate something to match with the error you’ve reported, so keep on warning us when a compilation/link error is not caught by the parsers!