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] Source loop identification
- Subject: [Frama-c-discuss] Source loop identification
- From: dhekir at gmail.com (Daniel Garcia)
- Date: Tue, 11 Jun 2013 09:46:09 +0200
Hi, Some time ago someone told me about loop instrumentation using a source code analysis tool, and I think it was Frama-C he mentioned, but I don't remember it clearly. What I'd like to do is to identify, on the source code, which lines correspond to a loop body and which are outside the loop (only considering structured loops here). I've been looking for something like this on the Frama-C GUI and manual, but couldn't find it. Is there such a thing on Frama-C, or am I mistaken about this feature? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20130611/f0c85c5e/attachment.html>
- Follow-Ups:
- [Frama-c-discuss] Source loop identification
- From: virgile.prevosto at m4x.org (Virgile Prevosto)
- [Frama-c-discuss] Source loop identification
- From: boris at yakobowski.org (Boris Yakobowski)
- [Frama-c-discuss] Source loop identification
- Prev by Date: [Frama-c-discuss] [Reminder] Frama-C tutorials
- Next by Date: [Frama-c-discuss] Source loop identification
- Previous by thread: [Frama-c-discuss] [Reminder] Frama-C tutorials
- Next by thread: [Frama-c-discuss] Source loop identification
- Index(es):