[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC 5/8] static-analyzer: Enforce coroutine_fn restrictions on func
|
From: |
Alberto Faria |
|
Subject: |
Re: [RFC 5/8] static-analyzer: Enforce coroutine_fn restrictions on function pointers |
|
Date: |
Mon, 4 Jul 2022 19:04:40 +0100 |
On Mon, Jul 4, 2022 at 6:46 PM Víctor Colombo
<victor.colombo@eldorado.org.br> wrote:
> Yes, this line is present at the beginning of the output
> Is this caused by problems with the code being analyzed or is it because
> libclang is getting confused with something that is outside of our
> control?
I think I found the problem: the commands in the compilation database
weren't being parsed properly. I switched to shlex.split() and it
seems to be working now. The WIP v2 is available at [1], if you want
to give it a try.
Thanks for reporting this!
Alberto
[1] https://gitlab.com/albertofaria/qemu/-/tree/static-analysis
- [RFC 1/8] Add an extensible static analyzer, (continued)
- [RFC 1/8] Add an extensible static analyzer, Alberto Faria, 2022/07/02
- [RFC 2/8] Drop some unused static function return values, Alberto Faria, 2022/07/02
- [RFC 3/8] static-analyzer: Enforce coroutine_fn restrictions for direct calls, Alberto Faria, 2022/07/02
- [RFC 4/8] Fix some direct calls from non-coroutine_fn to coroutine_fn, Alberto Faria, 2022/07/02
- [RFC 5/8] static-analyzer: Enforce coroutine_fn restrictions on function pointers, Alberto Faria, 2022/07/02
[RFC 6/8] Fix some coroutine_fn indirect calls and pointer assignments, Alberto Faria, 2022/07/02
[RFC 7/8] block: Add no_coroutine_fn marker, Alberto Faria, 2022/07/02
[RFC 8/8] Avoid calls from coroutine_fn to no_coroutine_fn, Alberto Faria, 2022/07/02
Re: [RFC 0/8] Introduce an extensible static analyzer, Paolo Bonzini, 2022/07/02
Re: [RFC 0/8] Introduce an extensible static analyzer, Daniel P . Berrangé, 2022/07/04