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] Questions about the Lithium beta 1 release
- Subject: [Frama-c-discuss] Questions about the Lithium beta 1 release
- From: david.delmas at airbus.com (David DELMAS)
- Date: Tue Dec 2 12:53:57 2008
Dear all, I would like to ask a few questions. 1. On dynamic plugins. 1.1. We are very happy with this feature, but it works only in bytecode mode (Lithium beta 1). Will it eventually work with native code also? 1.2. We have expressed (offline) the need for specific "hooks" in Frama-C: - when variables are being renamed because of scope issues; - when implicit casts are being made explicit; - when enumerated values are being replaced by integer constants. Are you working on this? When do you hope to release a version implementing such features? (even an intermediate CVS version) 2. On machine dependent parameters. One of the tool general options reads: -machdep machine : use [machine] as the current machine dependent configuration. Can you tell me more on how to fill in this configuration file? Section 2.4.2 of http://frama-c.cea.fr/download/frama-c-manual-Lithium- en.pdf claims "an autodetection program is provided in order to check the hypotheses mentioned in section 2.4.1, as well as to detect the endianness of the target and size of each C type". I failed to find such a program. Could you tell me more on this? 3. On install issues. 3.1. http://frama-c.cea.fr/download.html claims Frama-C Lithium will also soon be available through the GODI package manager. Unless I am mistaken, you haven't done so yet. Are you planning to do it soon? 3.2. We have been able to run Frama-C on Linux RHEL 4 untill Helium-20080701+dev2, but on the GUI no longer works with Lithium-20081001+alpha1 and with Lithium-20081002+beta1. This is a nuisance, because it is hard to experiment on impact analysis that way. Thanks endeed for your help! David The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other then the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
- Follow-Ups:
- [Frama-c-discuss] RE : [support-caveat] Questions about the Lithium beta 1 release
- From: Pascal.CUOQ at cea.fr (CUOQ Pascal)
- [Frama-c-discuss] RE : [support-caveat] Questions about the Lithium beta 1 release
- Prev by Date: [Frama-c-discuss] Dynamic Plugin
- Next by Date: [Frama-c-discuss] Dynamic Plugin
- Previous by thread: [Frama-c-discuss] Dynamic Plugin
- Next by thread: [Frama-c-discuss] RE : [support-caveat] Questions about the Lithium beta 1 release
- Index(es):