| A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering (FASE), volume 2029. |
....StackGuard [3] and many other recent implementations focus on preventing well known security holes such as stack bu#er overflow used by many recent security attacks. However, all of them detect only some common patterns of memory misuse, so complete safety is not guaranteed. Loginov et al. [10] proposes a method to keep pointer safety by adding a 4 bit tag to every octet in the working memory. Backward compatible bounds checking by Jones and Kelly [7] have modified gcc compiler to insert bounds checking code which uses a table of live objects. By their approach, it is impossible to ....
Alexey Loginov, Suan Hsi Yong, Susan Horwitz, and Thomas Reps. Debugging via run-time type checking. Lecture Notes in Computer Science, 2029:217--, 2001.
....(static) pointer declarations which were inferred SAFE, SEQ and DYNAMIC, respectively. gorithm we used CCured with a naive inference algorithm that makes all pointers DYNAMIC. The slowdown in this case is more signi cant (6 to 20 times slower) and it approaches that reported by other researchers [2, 13, 18, 19] who tried an allrun time checks approach to memory safety for C. For example, the most pointer intensive benchmark is li, which runs 16 times slower if all pointers are blindly marked DYNAMIC; however, once the inference discovers that all the pointers are SAFE or SEQ, it is only twice as slow. ....
....This results in a slowdown factor of 5 to 6. Fischer and Patil have presented a system that uses a second processor to perform the bounds checks [19] The total execution overhead of a program is typically only 5 using their technique but it requires a dedicated second processor. Loginov et al. [18] store type information with each memory location, incurring a slowdown factor of 5 to 158. This extra information allows them to perform more detailed checks and they can detect when stored types mismatch declared types or union members are accessed out of order. While their tool and ours are ....
A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Proceedings of FASE
....However, if the original program contains an unclean string expression, then the instrumented program will abort on an assert statement, while the result of the original program is unde ned. The idea of instrumenting programs to dynamically check cleanness is not new. For example, SafeC [1] and [12] also instruments the C source with assertions. Purify [14] instruments the executable les. These tools instrument every physical bu er by extending it with additional information and checking this additional information at runtime. Our approach is to instrument the program, adding computations ....
....to C. A total of 19 errors were detected with only four false alarms. See Table 3 and Section 4.3 for more information on the analysis results) 1. 2 Related Work Many academic and commercial projects aim at producing tools that detect string manipulation cleanness violations at runtime, e.g. [14, 1, 12]. Due to the overhead of runtime checking, these tools are usually not used in production. Moreover, their e ectiveness strongly depends on the input tested, and these checks do not assure against future bugs on di erent inputs. There are tools that directly identify cleanness violations leading ....
[Article contains additional citation context not shown here]
A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Proc. of Fundamental Approaches to Softw. Eng. (FASE), 2001.
No context found.
A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering (FASE), volume 2029.
No context found.
A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering, volume 2029.
No context found.
A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering (FASE), volume 2029.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. W. Reps. Debugging via run-time type checking. In Proc. Int. Conf. Fundamental Approaches to Software Engineering, pages 217--232, Apr. 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering, 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering, 2001.
No context found.
A. Loginov, S. Yong, S. Horwitz, , and T. Reps. Debugging via run-time type checking. In Proceedings of FASE 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. W. Reps. Debugging via run-time type checking. In International Conference on Fundamental Approaches to Software Engineering, April 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. W. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering, pages 217--232, April 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. W. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering, pages 217--232, April 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. W. Reps. Debugging via run-time type checking. In International Conference on Fundamental Approaches to Software Engineering, April 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. W. Reps. Debugging via run-time type checking. In International Conference on Fundamental Approaches to Software Engineering, April 2001.
No context found.
A. Loginov, S. Yong, S. Horwitz, , and T. Reps. Debugging via run-time type checking. In Proceedings of FASE 2001.
No context found.
Alexey Loginov, Suan Hsi Yong, Susan Horwitz, and Thomas Reps. Debugging via run-time type checking. In 4th International Conference on Fundamental Approaches to Software Engineering, volume 2029.
No context found.
A. Loginov, S.H. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Proceedings of FASE 2001: Fundamental Approaches to Software Engineering, April 2001.
No context found.
A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Proceedings of FASE 2001.
No context found.
A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Proceedings of FASE 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. W. Reps. Debugging via run-time type checking. In Fundamental Approaches to Software Engineering, pages 217-232, 2001.
No context found.
A. Loginov, S. H. Yong, S. Horwitz, and T. W. Reps. Debugging via run-time type checking. In International Conference on Fundamental Approaches to Software Engineering, April 2001.
No context found.
A. Loginov, S. Yong, S. Horwitz, and T. Reps. Debugging via run-time type checking. In Proceedings of FASE 2001.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC