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] Jessie: transpose_location_list => assert false
- Subject: [Frama-c-discuss] Jessie: transpose_location_list => assert false
- From: dillon.pariente at dassault-aviation.fr (Dillon Pariente)
- Date: Fri, 20 Nov 2009 15:32:12 +0100
- In-reply-to: <4B05679D.1000007@gmail.com>
- References: <AEF3FB2726363B4CB096A240443255101CCFB2@SCTEX008.st-cloud.dassault-avion.fr> <EF72DB711B17074BAB55287E04992AC0014FEE148405@CROEXCFWP04.gemalto.com> <4B05679D.1000007@gmail.com>
(Ooops! Previous mail below sent by me but from colleague's mail account by error. Sorry for confusion.) Back to my problem, Frama-C's Slicer made the job indeed, as - fortunately - regions of interest preserved by the slicer were of different types. So Jessie was able to analyze the sliced code without error. Not sure this is of huge interest for everybody (as it can not be generalized) ... but it makes some advertisement for this excellent Frama-C's Slicer, not so often discussed in this list! D. johcrown a ?crit : > Thank you very much for that hint! > Yes it "locally" works for this simple example. > But for the whole real code, I'm afraid I need region separation. > > After a quick check, it is an "old" bug already known in BTS (several > times it seems #80,112,303,31,106,39?) ... I won't add another issue! > > D. >
- References:
- [Frama-c-discuss] Jessie: transpose_location_list => assert false
- From: Dillon.Pariente at dassault-aviation.com (Pariente Dillon)
- [Frama-c-discuss] Jessie: transpose_location_list => assert false
- From: Nicolas.Rousset at gemalto.com (Rousset Nicolas)
- [Frama-c-discuss] Jessie: transpose_location_list => assert false
- From: johcrown at gmail.com (johcrown)
- [Frama-c-discuss] Jessie: transpose_location_list => assert false
- Prev by Date: [Frama-c-discuss] Windows binary version error: Global kernel could not find entry point: main
- Next by Date: [Frama-c-discuss] Using Frama-C as Caduceus
- Previous by thread: [Frama-c-discuss] Jessie: transpose_location_list => assert false
- Next by thread: [Frama-c-discuss] Global kernel could not find entry point: main
- Index(es):