Finding PathFinder



Email    print   
June 1, 2005 —  (Page 1 of 3)
Every so often I come across a piece of software that stuns me with its potential. Today’s example is Java PathFinder (javapathfinder.sourceforge.net), created by the Robust Software Engineering group at NASA Ames Research Center. I’d not heard of PathFinder until I read a recent press release saying that NASA had put it up on SourceForge, so I logged on to SourceForge just to find out what PathFinder was.

I’m impressed—and not just by the software itself, but by how making it open-source is exactly what’s needed for a valuable resource to reach its full potential. Open-sourcing PathFinder is a brilliant move on the part of NASA.

Without NASA’s original research, PathFinder simply wouldn’t exist. They’ve taken an interesting academic idea that’s been kicking around for a while—finding bugs in software by executing every possible (or at least reasonable) path through the code—and actually produced a program that finds a very-difficult-to-find bug that plagues every multithreaded program: deadlock (where two threads wait forever for each other to give up locks).

Anybody who has spent weeks trying to find a race condition that created a deadlock will immediately understand the importance of this accomplishment. The approach used to track down deadlock can also find other classes of bugs. Right now, PathFinder will find uncaught exceptions, for example, and the technology can be expanded to find other problems in your code.

PathFinder is not a testing framework like JUnit. It actually exercises the code for you, looking for bugs by running that code in a special-purpose VM. (That JVM, by the way, is written in Java. It’s an interesting notion—writing a JVM in Java.)

PathFinder is a research project, however, with no commercial applicability in its current state. The documentation, for example, reads like a dissertation—it’s way too dense to be useful as it stands. You have to be a developer to install the thing and get it running. The two other main shortcomings are a limited source-code size (of about 10K lines of code), which is really mandated by the technology, and an inability to process code that makes native-method calls (AWT, I/O code, etc.). The latter problem is easily solved—in fact, interfaces are provided to do a lot of the work—but these interfaces need to be implemented for all the standard libraries.




Pages 1 2 3 


Share this link: http://sdt.bz/28634
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Finding the right tool for the agile job
Experts emphasize that tools should bolster the agile process above all else Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb