Sciweavers

180 search results - page 19 / 36
» Locating causes of program failures
Sort
View
POS
1994
Springer
14 years 26 days ago
Hardware Support for Stability in a Persistent Architecture
Persistent stores support uniform management of data objects regardless of their lifetimes and locations. Such stores typically maintain a self-consistent state even after failure...
Frans A. Henskens, D. M. Koch, Rasool Jalili, John...
ICSE
2009
IEEE-ACM
14 years 9 months ago
Modular string-sensitive permission analysis with demand-driven precision
In modern software systems, programs are obtained by dynamically assembling components. This has made it necessary to subject component providers to access-control restrictions. W...
Emmanuel Geay, Marco Pistoia, Takaaki Tateishi, Ba...
SIGCSE
2006
ACM
119views Education» more  SIGCSE 2006»
14 years 2 months ago
Practice what you preach: full separation of concerns in CS1/CS2
We argue that the failure to separate the concerns in CS1 is the leading cause of difficulty in teaching OOP in the first year. We show how the concerns can be detangled and prese...
Hamzeh Roumani
COMPSAC
2005
IEEE
14 years 2 months ago
Autonomous Hot Patching for Web-Based Applications
Patching technologies are commonly applied to improve the dependability of software after release. This paper proposes an autonomous hot patching (AHP) framework to fully automate...
Hai Huang, Wei-Tek Tsai, Yinong Chen
ICST
2010
IEEE
13 years 7 months ago
Automated Bug Neighborhood Analysis for Identifying Incomplete Bug Fixes
—Although many static-analysis techniques have been developed for automatically detecting bugs, such as null dereferences, fewer automated approaches have been presented for anal...
Mijung Kim, Saurabh Sinha, Carsten Görg, Hina...