From: Norbert Manthey <nmanthey@amazon.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Norbert Manthey <norbertmanthey@googlemail.com>,
smatch@vger.kernel.org, jsteckli@amazon.com,
tautschn@amazon.co.uk
Subject: Re: Smatch for Xen
Date: Wed, 15 Aug 2018 15:44:06 +0200 [thread overview]
Message-ID: <66e81e7b-de2c-cfa1-5ed8-98cb76ff08c3@amazon.de> (raw)
In-Reply-To: <20180815090348.nywfrystuytf2ta3@mwanda>
I see. I assume smatch does not print output in parallel, so that mix
results from one-line-scan compiling the same file multiple times, and
those calls compete wrt writing to that file.
As the output might be broken, could we agree on using the --file-output
option for now, and I see how I can fix the mixed output problem best?
Best,
Norbert
On 08/15/2018 11:03 AM, Dan Carpenter wrote:
> I have an issue where the output is getting a bit jumbled when I build
> with --info.
>
> /home/dcarpenter/progs/src/xen/xen/xen/arch/x86/mm/shadow/multi.c:4777 sh_audit_fl1_table__guest_2() SQL_caller_info: insert into caller_info values ('/home/dcarpenter/progs/src/xen/xen/xen/arch/x86/mm/shadow/multi.c', 'sh_audit_fl1_table__guest_2', 'guest_index', %CALL_ID%, 1, 0, -1, '%call_marker%', /shadow/multi.c:3340 sh_page_fault__guest_4() SQL_caller_info: insert into caller_info values ('/home/dcarpenter/progs/src/xen/xen/xen/arch/x86/mm/shadow/multi.c', 'sh_page_fault__guest_4', 'sh_audit_gw', %CALL_ID%, 1, 1001, 0, '$->domain->arch.paging.shadow.has_fast_mmio_entries', '1');
>
> It's mixing line 4777 with 3340.
>
> regards,
> dan carpenter
>
Amazon Development Center Germany GmbH
Berlin - Dresden - Aachen
main office: Krausenstr. 38, 10117 Berlin
Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger
Ust-ID: DE289237879
Eingetragen am Amtsgericht Charlottenburg HRB 149173 B
prev parent reply other threads:[~2018-08-15 16:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 12:40 Smatch for Xen Norbert Manthey
2018-07-30 16:34 ` [PATCH 0/3] add support for mode __pointer__ & __byte__ Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 1/3] mode keywords don't need MOD_{CHAR,LONG,...} Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 2/3] add support for mode __pointer__ Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 3/3] add support for mode __byte__ Luc Van Oostenryck
2018-08-06 10:31 ` Smatch for Xen Dan Carpenter
2018-08-06 11:20 ` Dan Carpenter
2018-08-06 13:16 ` Dan Carpenter
[not found] ` <CAByO1we3OABkX8XCwh7Vq8iHyXAuFtJ3t+Ta3DVCLe9pP6K8ew@mail.gmail.com>
2018-08-06 13:54 ` Dan Carpenter
2018-08-13 14:25 ` Norbert Manthey
2018-08-13 17:58 ` Dan Carpenter
2018-08-13 18:31 ` Dan Carpenter
2018-08-14 13:27 ` Norbert Manthey
2018-08-14 14:21 ` Dan Carpenter
2018-08-14 14:33 ` Norbert Manthey
2018-08-14 14:52 ` Dan Carpenter
2018-08-14 15:05 ` Norbert Manthey
2018-08-15 9:03 ` Dan Carpenter
2018-08-15 13:44 ` Norbert Manthey [this message]
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=66e81e7b-de2c-cfa1-5ed8-98cb76ff08c3@amazon.de \
--to=nmanthey@amazon.de \
--cc=dan.carpenter@oracle.com \
--cc=jsteckli@amazon.com \
--cc=norbertmanthey@googlemail.com \
--cc=smatch@vger.kernel.org \
--cc=tautschn@amazon.co.uk \
/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).