Frama-C-discuss mailing list archives
This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Frama-c-discuss] gWhy timeout
- Subject: [Frama-c-discuss] gWhy timeout
- From: hollas at informatik.htw-dresden.de (Boris Hollas)
- Date: Mon, 11 Oct 2010 16:07:42 +0200
Hello, the prover timeout for gWhy doesn't work on my system. I set it to 1 s in the GUI, yet it still takes 10 s for alt-ergo to timeout. Is there a fix for that? Also, is it possible to set the timeout permanently? gWhy forgets the setting upon the next start. I use Ubuntu 10 + beryllium 2 + alt-ergo 0.92. BTW, have you considered using iterative deepening instead? This way, the user could very quickly see which VCs may not verify and start debugging. In the rare case that a VC can be verified with some more time, the user would be informed some seconds later. This may save a lot of time. -- Regards, Boris
- Follow-Ups:
- [Frama-c-discuss] gWhy timeout
- From: hollas at informatik.htw-dresden.de (Boris Hollas)
- [Frama-c-discuss] gWhy timeout
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- [Frama-c-discuss] gWhy timeout
- Prev by Date: [Frama-c-discuss] Fedora 13 and 14
- Next by Date: [Frama-c-discuss] gWhy timeout
- Previous by thread: [Frama-c-discuss] Fedora 13 and 14
- Next by thread: [Frama-c-discuss] gWhy timeout
- Index(es):