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] what to do when Frama-c tells me to submit a bug
- Subject: [Frama-c-discuss] what to do when Frama-c tells me to submit a bug
- From: christoph.weber at first.fraunhofer.de (Christoph Weber)
- Date: Fri, 11 Sep 2009 10:24:08 +0200
- References: <4A9E1CB6.7050000@cea.fr><FC0686BB6178BC43B9DC035287A11A720DBC0324AB@SI-MBX12.de.bosch.com><EF56E4EC-4965-4189-8529-699FAC3931F8@cea.fr><FC0686BB6178BC43B9DC035287A11A720DBC032FA6@SI-MBX12.de.bosch.com><5EFD4D7AC6265F4D9D3A849CEA9219191AB206@LAXA.intra.cea.fr> <2F39448A-1A63-4C54-B126-E79EDD70B6D3@first.fraunhofer.de>
Hello, I would like to know what I have to do when Frama-c tells me to submit sth. to the bts. That was my call: $ frama-c -jessie max.h [kernel] preprocessing with "gcc -C -E -I. -dD max.h" [jessie] Starting Jessie translation [jessie] user error: Nothing to process. There was probably an error before. max.h:27:[jessie] failure: Unexpected exception. Please submit bug report (Ref. "Log.AbortError("jessie")"). [kernel] Plugin jessie aborted because of an internal error. Please report with 'crash' at http://bts.frama-c.com Obviously, the analysis of .h files is no longer supported and will cause an error. By the way, I would prefer to analyse .h files as well, this would allow me to check the function contract for syntactical errors. Ok, back to my question: What shall I submit? Is there a file created by frama-c , if so, I cannot find it. And if there is no bugreport created by frama-c I think it would be a good Idea to let frama-c create a file, I could mail to you. Otherwise, I would have no Idea what to post. If you have already something like a microsoft of mozilla bug reporting system, I would like to know how to use it. If not, I believe it would be beneficial for both, the user and the developer. Sincerely Christoph -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/ms-tnef Size: 3637 bytes Desc: not available Url : http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20090911/d461c830/attachment.bin
- Follow-Ups:
- [Frama-c-discuss] what to do when Frama-c tells me to submit a bug
- From: Pascal.CUOQ at cea.fr (CUOQ Pascal)
- [Frama-c-discuss] what to do when Frama-c tells me to submit a bug
- References:
- [Frama-c-discuss] Release Beryllium 20090901
- From: benjamin.monate at cea.fr (Benjamin Monate)
- [Frama-c-discuss] Release Beryllium 20090901
- From: Boris.Hollas at de.bosch.com (Hollas Boris (CR/AEY1))
- [Frama-c-discuss] Release Beryllium 20090901
- From: Pascal.Cuoq at cea.fr (Pascal Cuoq)
- [Frama-c-discuss] Release Beryllium 20090901
- From: Boris.Hollas at de.bosch.com (Hollas Boris (CR/AEY1))
- [Frama-c-discuss] Release Beryllium 20090901
- From: Pascal.CUOQ at cea.fr (CUOQ Pascal)
- [Frama-c-discuss] Release Beryllium 20090901
- From: jens.gerlach at first.fraunhofer.de (Jens Gerlach)
- [Frama-c-discuss] Release Beryllium 20090901
- Prev by Date: [Frama-c-discuss] Beryllium Jessie - Type Invariants
- Next by Date: [Frama-c-discuss] Alt-ergo Problems
- Previous by thread: [Frama-c-discuss] Release Beryllium 20090901
- Next by thread: [Frama-c-discuss] what to do when Frama-c tells me to submit a bug
- Index(es):