Author Topic: Incorrect compiler output parsing  (Read 4663 times)

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Incorrect compiler output parsing
« on: November 20, 2011, 05:39:19 am »
It seems that the "Preprocessor error" regular expression is matching compiler notes emitted from MinGW 4.6 (TDM).
The following is a section of my build log, in which Code::Blocks will jump to the line after the compile process has finished (marking it as an error).
Quote
mingw32-g++.exe -g -pipe -mthreads -fmessage-length=0 -fexceptions -Winvalid-pch -DHAVE_W32API_H -D__WXMSW__ -DWXUSINGDLL -DBUILDING_PLUGIN -DcbDEBUG -DCB_PRECOMP -DWX_PRECOMP -DwxUSE_UNICODE -DWXMAKINGDLL_PROPGRID -DwxPG_USE_WXMODULE=0 -fexpensive-optimizations -O3 -IC:\Libraries\wxWidgets28\include -IC:\Libraries\wxWidgets28\lib\gcc_dll\mswu -IC:\Libraries\wxWidgets28\contrib\include -I..\..\..\include -I..\..\..\sdk\wxscintilla\include -c C:\Libraries\cb\src\plugins\contrib\headerfixup\defaults.cpp -o ..\..\..\.objs\plugins\contrib\headerfixup\defaults.o
C:\Libraries\cb\src\plugins\contrib\headerfixup\defaults.cpp: In member function 'void Bindings::SetDefaultsWxWidgets()':
C:\Libraries\cb\src\plugins\contrib\headerfixup\defaults.cpp:300:6: note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without
mingw32-g++.exe -g -pipe -mthreads -fmessage-length=0 -fexceptions -Winvalid-pch -DHAVE_W32API_H -D__WXMSW__ -DWXUSINGDLL -DBUILDING_PLUGIN -DcbDEBUG -DCB_PRECOMP -DWX_PRECOMP -DwxUSE_UNICODE -DWXMAKINGDLL_PROPGRID -DwxPG_USE_WXMODULE=0 -fexpensive-optimizations -O3 -IC:\Libraries\wxWidgets28\include -IC:\Libraries\wxWidgets28\lib\gcc_dll\mswu -IC:\Libraries\wxWidgets28\contrib\include -I..\..\..\include -I..\..\..\sdk\wxscintilla\include -c C:\Libraries\cb\src\plugins\contrib\headerfixup\execution.cpp -o ..\..\..\.objs\plugins\contrib\headerfixup\execution.o


Offline Jenna

  • Administrator
  • Lives here!
  • *****
  • Posts: 7252
Re: Incorrect compiler output parsing
« Reply #1 on: November 20, 2011, 09:43:36 am »
This should work correctly on a recent C::B from trunk (aka nightly).
Just tested with your warning on a version from my repo.
It is correctly recognized as info-message on line 300.

Which revision do you use ?

Do you have any changed regexes in th "Output parsing" section of advanced compiler settings ?

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: Incorrect compiler output parsing
« Reply #2 on: November 20, 2011, 08:51:12 pm »
You are right (I did not think to check before I posted).
I had been maintaining two sets of Code::Blocks' source code on my hard-drive: one to make patches against, and one to compile plugins against.  Unfortunately, while I had kept the one for patches up to date, I forgot to update the one for plugins.  (It was all the way back at r7460!)

Updated the second set to r7597 -> everything works as expected (although, it seems I will have to update the API my plugin uses).

Thank you.