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] Frama-C: GUI's response time

  • Subject: [Frama-c-discuss] Frama-C: GUI's response time
  • From: Dillon.Pariente at dassault-aviation.com (Pariente Dillon)
  • Date: Thu, 2 Apr 2009 11:11:31 +0200
Dear All,
 
I'm currently working on a larger source code of about 100 functions,
for a total of 10K Sloc.
Value Analysis is performed on the whole code through a classical
command line like:
frama-c-gui -val ... 
 
After some computations (~40 minutes elapsed time), Frama-C's GUI is
displayed.
But when selecting a particular function from one of the 80 different
source files, even the smallest one, the GUI gets stuck for a long
period of time (for some analysis, it seems to be "infinite").
On smaller application, response time is of course a lot smaller.
 
During these long period of time, Windows' Task manager shows
frama-c-gui.exe using 99% of CPU with an almost constant use of 490 Mo
of RAM.
 
Do you have any experience of GUI exploring medium size applications and
showing such a behavior?
Is there any hint to instrument some parts of GUI's code, in such a way
to identify its origin?
 
Thanks in advance for your help!
 
Best regards,
Dillon PARIENTE
 
(Configuration: OCaml port for Cygwin (not yet MinGW!), Windows XP, PC
2GHz 2GoRAM)
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20090402/5516961b/attachment-0001.htm