cXprop users Google Group

Re: cXprop/CComp: reporting 2 bugs

2009-01-31T20:02:23Z

Aurélien -
I looked into the two bugs you mentioned today. Unfortunately, the first
problem occurs inside CIL's parser and not in cXprop. The current
version of CIL still does not deal with labels for operands in inline
assembly, and adding that feature to their parser is beyond what I have
time to do. If you were to get it updated in CIL, I could then update

Updated instructions for CComp

2008-04-15T18:41:17Z

Thanks to a bug report from Fernando Magno Quintao Pereira at UCLA, I
found out the posted CComp distribution has a number of bugs. I updated
the distribution and the instructions. Sorry.

New pdfs

2008-03-13T16:24:44Z

I put up pdf versions of a number of the talks we have done about cXprop
and CComp.
[link]
[link]

New slides!

2008-01-21T17:24:29Z

John Regehr presented the research behind cXprop this past weekend at
the Washington University in St. Louis. You can find the slides here:
[link]

Re: [cXprop] Substantial update pending

2007-12-13T18:15:49Z

The new version of cXprop is up and running, and this page has been
updated here and there to reflect changes I have made. Please email me
with complaints, comments, and suggestions!
[link]

Substantial update pending

2007-12-13T16:57:05Z

John Regehr submitted a bug last night that led me to discover I had
accidentally written over the native machine dependency file. So anybody
running cXprop for normal desktop programs has probably been getting
incorrect answers.
This bug has been lurking since I added the 8051 machine dependency file

Sydney talk

2007-11-20T17:25:31Z

John Regehr presented our work for cXprop in Sydney Australia earlier
this month. The slides for that presentation can be found here:
[link]
Most of this describes work we have already done, but the triggering and
sequencing ideas are future work.

Re: [cXprop] output of state

2007-11-16T20:21:50Z

I just posted a version of cXprop which adds global state to the
information printed by using the --cxp_global_states flag. Sorry this
was not in the version posted earlier this week.
[link]
Let me know if you have any questions or problems.
Nathan

Re: [cXprop] output of state

2007-11-16T17:25:02Z

This is a feature that I am in the middle of adding at various people's
request. There are two partial solutions:
--cxp_global_states
Prints the state at the start of each function, plus the return value,
to a file with .states added to the end. Each function is identified,
and then the output is of the form:

output of state

2007-11-16T11:55:02Z

Hi Nathan,

I'm posting here in case other users have similar questions.
Is there a way to output the abstract variable state after the
analysis ? E.g. when using the interval domain it would output { l =
[0 20], h = [1 19], ... } or something.

thanks
Jonathan

Updated version

2007-11-13T20:49:53Z

I updated the source download on the CComp website. So the current
version of cXprop/CComp can be found here:
[link]

John's talk on CComp

2007-11-01T20:33:35Z

I put John's slides for his upcoming talk on RAM compression on the website:
[link]

CIL tools for TinyOS

2007-04-27T19:57:48Z

I just put together a web page which has simplified binaries and scripts
for running our static analysis tools on TinyOS code. It is designed to
help people get started easier at using our tools:
[link]

CComp and other updates

2007-04-26T21:07:13Z

I have just expanded the CComp web page to be somewhat useful:
[link]
CComp extends cXprop to do offline compression of on-chip RAM. There is
a link on the page to our paper describing this technique.
If you haven't visited the cXprop page in a while, it is still here:

Another test

2006-02-18T15:33:47Z

Testing again.

Test

2005-09-14T20:38:14Z

This is a test message.