Problems stepping through PC-lint output

Problems stepping through PC-lint output

[Sarir Khamsi]

I am using GNU Emacs (22.0.50.20) on WinXP, SP2 to step through the
output of PC-lint using the Emacs "next-error" command but am having
problems. First, I execute "compilation-mode" on the PC-lint output
file to get into, well, compilation mode (this also changes the colors
of the warnings, errors, info, etc). Next, I step through the output
with the "next-error" command, as mentioned, but some of the output
gets skipped entirely. That is, when I press "next-error" to have
Emacs go to the source code where the next "error" is, some lines in
the PC-lint output get skipped.

For example, given the lines

   --- Module:   Vehicle.cpp
               _
   #define D2R 0.0174532925199433
   MathGlobals.h:41:12: Note 1923: macro 'D2R' could become const variable --
       Effective C++ #1
                 _
   #define R2D 1/D2R
   MathGlobals.h:42:14: Info 773: Expression-like macro 'R2D' not parenthesized
   MathGlobals.h:42:14: Note 1923: macro 'R2D' could become const variable --
       Effective C++ #1
                      _
      d_IParam(double);
   ConcreteTypes.hpp:21:19: Note 1931: Constructor 'd_IParam::d_IParam(double)'
       can be used for implicit conversions -- More Effective C++ #5
                   _
      i_IParam(int);

the "MathGlobals.h:42:14: Info 773" line will get skipped and Emacs
will jump to the next message (in this case, the second "Note 1923"
about R2D). I am using

-"format=%(%f:%l:%c: %)%t %n: %m"

in my options.lnt file for PC-lint (per some instructions on the web),
which helped get this working at all, but I can't see why lines are
getting skipped. Any ideas? Thanks.

Sarir

-- 
Sarir Khamsi
email: sarir.khamsi@raytheon.com

Re: Problems stepping through PC-lint output

[Eli Zaretskii]

> From: Sarir Khamsi <sarir.khamsi@raytheon.com>
> Date: Thu, 03 Nov 2005 15:10:34 -0700
> 
> I am using GNU Emacs (22.0.50.20) on WinXP, SP2

Problems with the CVS version of Emacs should be posted to
emacs-devel@gnu.org, not here.

> For example, given the lines
> 
>    --- Module:   Vehicle.cpp
>                _
>    #define D2R 0.0174532925199433
>    MathGlobals.h:41:12: Note 1923: macro 'D2R' could become const variable --
>        Effective C++ #1
>                  _
>    #define R2D 1/D2R
>    MathGlobals.h:42:14: Info 773: Expression-like macro 'R2D' not parenthesized
>    MathGlobals.h:42:14: Note 1923: macro 'R2D' could become const variable --
>        Effective C++ #1
>                       _
>       d_IParam(double);
>    ConcreteTypes.hpp:21:19: Note 1931: Constructor 'd_IParam::d_IParam(double)'
>        can be used for implicit conversions -- More Effective C++ #5
>                    _
>       i_IParam(int);
> 
> the "MathGlobals.h:42:14: Info 773" line will get skipped and Emacs
> will jump to the next message (in this case, the second "Note 1923"
> about R2D).

I suspect that this is because "info:" is special to the compilation
messages parser.  See the file etc/compilation.txt in the Emacs
distribution.

If you post this to emacs-devel, the Emacs developers will look at the
problem and try to fix it.

Re: Problems stepping through PC-lint output

[Sarir Khamsi]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Sarir Khamsi <sarir.khamsi@raytheon.com>
>> Date: Thu, 03 Nov 2005 15:10:34 -0700
>> 
>> I am using GNU Emacs (22.0.50.20) on WinXP, SP2
>
> Problems with the CVS version of Emacs should be posted to
> emacs-devel@gnu.org, not here.

OK, but I didn't think it was an Emacs problem, but instead, a PC-lint
setup problem. I'll try the list.

> I suspect that this is because "info:" is special to the compilation
> messages parser.  See the file etc/compilation.txt in the Emacs
> distribution.

Thanks, that gives me something to look at.

Sarir

Re: Problems stepping through PC-lint output

[Stefan Monnier]

> the "MathGlobals.h:42:14: Info 773" line will get skipped and Emacs
> will jump to the next message (in this case, the second "Note 1923"
> about R2D). I am using

Maybe it's because it's just an information message.  Take a look at
compilation-skip-threshold (or rather, read the NEWS file).


        Stefan