From: Sarir Khamsi <sarir.khamsi@raytheon.com>
Subject: Problems stepping through PC-lint output
Date: Thu, 03 Nov 2005 15:10:34 -0700 [thread overview]
Message-ID: <u4q6t5qn9.fsf@raytheon.com> (raw)
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
next reply other threads:[~2005-11-03 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 22:10 Sarir Khamsi [this message]
2005-11-04 11:04 ` Problems stepping through PC-lint output Eli Zaretskii
[not found] ` <mailman.13922.1131102300.20277.help-gnu-emacs@gnu.org>
2005-11-04 17:17 ` Sarir Khamsi
2005-11-22 19:59 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u4q6t5qn9.fsf@raytheon.com \
--to=sarir.khamsi@raytheon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).