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] Getting a node from its id for a particular pdg
- Subject: [Frama-c-discuss] Getting a node from its id for a particular pdg
- From: julien.signoles at cea.fr (Julien SIGNOLES)
- Date: Wed, 18 Mar 2009 17:02:36 +0100
- In-reply-to: <49C116F4.5050507@sophia.inria.fr>
- References: <1237387890.3508.114.camel@supelec> <49C116F4.5050507@sophia.inria.fr>
Bonjour, > Do you know that for simple cases like that, you should consider to use > [Db.Pdg.extract] to generate a .dot file so you can have a look at the > graph. I think it helps a lot at the beginning... You can also use some pdg internal options to better understand what really happened. Use 'frama-c -pdg-debug -help' to have the list of these options. For instance, 'frama-c -pdg-debug "-pdg -dot-pdg foo" bar.c' generates a file 'foo.f.dot' for each function 'f' of bar.c.
- References:
- [Frama-c-discuss] Getting a node from its id for a particular pdg
- From: jcdemay at rennes.supelec.fr (Jonathan-Christofer Demay)
- [Frama-c-discuss] Getting a node from its id for a particular pdg
- From: anne.pacalet at sophia.inria.fr (Anne Pacalet)
- [Frama-c-discuss] Getting a node from its id for a particular pdg
- Prev by Date: [Frama-c-discuss] Getting a node from its id for a particular pdg
- Next by Date: [Frama-c-discuss] Unability to verify an arithmetic assertion disapears in a reduced but similar test case
- Previous by thread: [Frama-c-discuss] Getting a node from its id for a particular pdg
- Next by thread: [Frama-c-discuss] Getting a node from its id for a particular pdg
- Index(es):