Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect Büchi program while using LTLAutomizerCInline toolchain #558

Open
jjoojjoo123 opened this issue Apr 22, 2021 · 4 comments
Open
Assignees

Comments

@jjoojjoo123
Copy link

I've tried some C programs with LTL property using LTLAutomizerC.xml and LTLAutomizerCInline.xml with jungvisualization plugin. However, the resulting Büchi program is not correctly generated while using LTLAutomizerCInline.xml toolchain, i.e. with Boogie procedureinliner plugin. The never claim automaton states do not appear in any states of the resulting Büchi program, so the LTL property is always satisfied whatever the input program and the property are. This issue is also mentioned in the update of #508. Thanks.

@danieldietsch
Copy link
Member

You are right, Ill look into it, but it might take some time because of deadlines ,)

Is this time-critical for you?

@jjoojjoo123
Copy link
Author

Probably yes. We want to do something with concurrent C program and LTL simultaneously, which requires the correct Büchi program product. In addition, the product generator seems not to recognize the thread related edges of RCFG. Will this take a lot of work ? Thank you so much.

@Langenfeld
Copy link
Member

The problem is, that the product generator ignores everything, that is of the ULTIMATE.start or .init functions. The inliner seems to set these functions for all the statements, that are inlined, thus they are ignored.

The good news is, that we fixed the several errors in the non-inlined ltl checking, so that might solve the problem, just try #566.

@danieldietsch
Copy link
Member

Adding support for multi-threaded programs is hard for numerous reasons. It wont be done quickly, but possibly this year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants