From: Dan Carpenter <dan.carpenter@linaro.org>
To: 李书畅 <lishuchang@hust.edu.cn>
Cc: smatch@vger.kernel.org
Subject: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Date: Wed, 13 Mar 2024 11:37:54 +0300 [thread overview]
Message-ID: <067d5097-0c78-4d57-bd5b-7bcace5949d3@moroto.mountain> (raw)
In-Reply-To: <26e4d1e9.17593.18e36ee36ee.Coremail.lishuchang@hust.edu.cn>
On Wed, Mar 13, 2024 at 04:29:25PM +0800, 李书畅 wrote:
> I see.
> And in this case, if I just want to check a single .c file other than the whole directory after building the database ,
> what should I do ?
It's going to depend on the build system. But normally:
rm path/to/file.o
make CHECK="/path/to/smatch --file-output" path/to/file.o
cat path/to/file.c.smatch
regards,
dan carpenter
next prev parent reply other threads:[~2024-03-13 8:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 5:28 about using smatch in all debian C code 李书畅
2023-11-09 7:57 ` Dan Carpenter
2024-03-06 6:12 ` 李书畅
2024-03-06 6:40 ` Dan Carpenter
2024-03-06 9:47 ` 李书畅
2024-03-06 18:40 ` Dan Carpenter
2024-03-06 19:25 ` Dan Carpenter
2024-03-07 3:43 ` 李书畅
2024-03-07 9:49 ` Dan Carpenter
2024-03-07 10:27 ` 李书畅
2024-03-10 4:56 ` 李书畅
2024-03-10 5:39 ` 李书畅
2024-03-11 5:00 ` Dan Carpenter
2024-03-11 13:23 ` 李书畅
2024-03-12 12:38 ` 李书畅
2024-03-12 14:22 ` 李书畅
2024-03-13 5:58 ` Dan Carpenter
2024-03-13 6:29 ` 李书畅
2024-03-13 7:29 ` Dan Carpenter
2024-03-13 7:51 ` 李书畅
2024-03-13 8:08 ` Dan Carpenter
2024-03-13 8:29 ` 李书畅
2024-03-13 8:37 ` Dan Carpenter [this message]
2024-03-22 7:05 ` 李书畅
2024-03-22 7:49 ` Dan Carpenter
2024-03-22 7:55 ` Dan Carpenter
2024-03-11 5:01 ` Dan Carpenter
2024-03-11 5:31 ` 李书畅
2024-03-11 7:39 ` Dan Carpenter
2024-03-11 7:54 ` 李书畅
2024-03-11 7:07 ` 李书畅
2024-03-11 7:33 ` Dan Carpenter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=067d5097-0c78-4d57-bd5b-7bcace5949d3@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=lishuchang@hust.edu.cn \
--cc=smatch@vger.kernel.org \
/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).