Nam H. Pham

Dear Nam, Tung, Hoan and Tien,

We are pleased to inform you that your paper

“Detection of Recurring Software Vulnerabilities”
(Paper-ID: ????)

has been accepted for publication as full paper in the proceedings of
the 25nd IEEE/ACM International Conference on Automated Software
Engineering (ASE 2010).

All papers went through a rigorous reviewing process and each paper
was reviewed by at least two reviewers.  Out of 191 submitted papers,
only 34 were accepted as full papers and another 31 as short papers.

In revising your paper, please pay attention to the reviewers’
comments below. The submission deadline for the camera-ready version
is July 8th.

Instruction for final submission of your paper including format,
copyright, etc. will be provided in a separate message.

Please note that at least one of the authors of the paper must
register for the conference. Otherwise, we will not be able to include
your paper in the proceedings.

Registration will open soon; please see the conference web site for
further information.

http://soft.vub.ac.be/ase2010/

Congratulations again on having your paper accepted and thank you for
your submission.  We look forward to meeting with you this September
in Antwerp.

Cheers,

Jamie and Elisabetta
ASE 2010 Program Chairs

Hi Cygwin friends and users,

after an exceptionally long time of development and testing we’re proud
to release Cygwin’s next major version 1.7.1.

This release is a big leap from the former Cygwin releases in a couple
of ways. For the full list we urge you to read the new User’s Guide,
which you can now find in the usual place:

http://cygwin.com/cygwin-ug-net/

There’s a “What’s new” section at

http://cygwin.com/cygwin-ug-net/ov-new1.7.html

The most important changes are:

- The mount table is no longer stored in the registry. Rather, it’s
stored in /etc/fstab and /etc/fstab/$USER. See
http://cygwin.com/cygwin-ug-net/using.html#mount-table

- Support for pathnames beyond the former 260 chars border. PATH_MAX
is now set to 4096, but Cygwin will try to support even longer paths
up to the Windows maxium of 32767 Unicode chars,

- Multiple Cygwin installations can co-exist on a machine, as long
as you keep them separate.

- Support for IPv6.

- Default character set is now UTF-8, but other character sets are
supported via an improved internationalization support. See
http://cygwin.com/cygwin-ug-net/setup-locale.html

- Support for new authentication methods which are supposed to improve
changing the user context without password.

- No more support for Windows 95, Windows 98 and Windows Me.

======================================================================
IMPORTANT NOTES for those who upgrade from an existing Cygwin 1.5.25
installation:

You *must* upgrade to the latest setup.exe from our main web page at
http://cygwin.com/

Moving the mount table from the registry to /etc/fstab works only
automatically for system mount points. User mount points have to be
taken care of manually, using the /usr/bin/copy-user-registry-fstab
script. See http://cygwin.com/cygwin-ug-net/using.html#mount-table
======================================================================

Have fun,
Corinna

Source: http://cygwin.com/ml/cygwin-announce/2009-12/msg00027.html

Comments: Frankly, I rarely used cygwin. Nevertheless, I find it handy recently when I want to use Perl & Unix commands. Even it’s not as convenient as in Linux, it’s small and enough for my needs. Moreover, I like the ideas creating an Unix environment inside Windows. It’s just like an idea of a wooden horse in Trojan War.

Way, after four hours reading, searching, andcoding, I finally understand how to use Eclipse C/C++ Development Tooling (CDT) to parse the C/C++ source code. In detail, it used the Document Object Model (DOM) to parse and update AST whenever there is a change in source file.

The reason I spent so much time solving this problem because of lack in APIs documentation and also I thought that the sample code using CDT is from old version (2.0) in which many APIs were deprecated.

Similar to JDT- the tool parse Java source code to build AST – CDT works in similar steps:

1. Create an IASTTranslationUnit instance
2. Overide abstract class ASTVisior
3. Traverse the IASTTranslationUnit using ASTVisior

Here are the sample code which works with Eclipse SDK 3.5.1 and CDT version 6.0.1:

Import:

1
2
3
4
5
6
7
8
9

import org.eclipse.cdt.core.dom.ICodeReaderFactory;
import org.eclipse.cdt.core.dom.ast.ASTVisitor;
import org.eclipse.cdt.core.dom.ast.IASTTranslationUnit;
import org.eclipse.cdt.core.dom.ast.gnu.cpp.GPPLanguage;
import org.eclipse.cdt.core.parser.CodeReader;
import org.eclipse.cdt.core.parser.DefaultLogService;
import org.eclipse.cdt.core.parser.IParserLogService;
import org.eclipse.cdt.core.parser.IScannerInfo;
import org.eclipse.cdt.core.parser.ScannerInfo;

Main program:

1
2
3
4
5
6
7
8
9
10
11
12
13

IParserLogService log = new DefaultLogService();
char[] code = readFile("C:\\grep.cpp");
CodeReader reader = new CodeReader(code);
Map definedSymbols = new HashMap();
String[] includePaths = new String[0];
IScannerInfo info = new ScannerInfo(definedSymbols, includePaths);
ICodeReaderFactory readerFactory = FileCodeReaderFactory.getInstance();
 
IASTTranslationUnit translationUnit = GPPLanguage.getDefault()
.getASTTranslationUnit(reader, info, readerFactory, null, log);
 
ASTVisitor visitor = new ImplASTVisitor();
translationUnit.accept(visitor);

Please note that I already override the ASTVisior class with my own one ImplASTVisitor:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

public class ImplASTVisitor extends ASTVisitor {
	public ImplASTVisitor(){
		super.shouldVisitNames = true;
		super.shouldVisitDeclarations = true;
		super.shouldVisitInitializers = true;
		super.shouldVisitParameterDeclarations = true;
		super.shouldVisitDeclarators = true;
		super.shouldVisitDeclSpecifiers = true;
		super.shouldVisitExpressions = true;
		super.shouldVisitStatements = true;
		super.shouldVisitTypeIds = true;
		super.shouldVisitEnumerators = true;
		super.shouldVisitTranslationUnit = true;
		super.shouldVisitProblems = true;
	}
 
	/**
	 * @return continue to continue visiting, abort to stop, skip to not descend
	 *         into this node.
	 */
	public final static int PROCESS_SKIP = 1;
	public final static int PROCESS_ABORT = 2;
	public final static int PROCESS_CONTINUE = 3;
	/**
	 *
	 * visit methods
	 *
	 */
	private void print(IASTNode node){
		System.out.println(node.getRawSignature());
	}
	public int visit(IASTTranslationUnit tu) {
		print(tu);
		return PROCESS_CONTINUE;
	}
	public int visit(IASTName name) {
		print(name);
		return PROCESS_CONTINUE;
	}
 
	public int visit(IASTDeclaration declaration) {
		print(declaration);
		return PROCESS_CONTINUE;
	}
       .....
}

I actually did not write all this portion of code. I read, understand and rewrite it based on the following sources:

• Thanks  Matthew Scarpino for this wonderful article: Building a CDT-based editor, Part 3: Basic CDT parsing

• Thanks Jason Montojo for this sample source code: Nabble