R. Hastings and B. Joyce. Purify: Fast Detection of Memory Leaks and Access Errors. In Winter USENIX Conference, pages 125--136, 1992. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
Reconsidering Custom Memory Allocation - Emery Berger Dept (2002) (1 citation) (Correct)
....bookkeeping burden on the programmer to ensure that objects are freed by the correct allocator. Custom allocators also can make it difficult to understand the sources of memory consumption in a program. Using custom allocators often precludes the use of memory leak detection tools like Purify [21]. Use of custom allocators also precludes the option of later substituting a parallel allocator to provide SMP scalability [3] a garbage collector to protect against memory leaks [29] or a shared multi language heap [42] However, custom memory allocators can provide some important software ....
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX 1992.
Improving Computer Security using Extended Static Checking - Chess (2002) (12 citations) (Correct)
....Kelly [16] propose a scheme for adding object bounds checks at compile time, but standard libraries that are not recompiled remain vulnerable to buffer overflow attacks, and the performance of checked programs may suffer. Similarly, program instrumentation approaches like the one taken by Purify [14] are usually impractical because of performance degradation and increased memory usage. Format string vulnerabilities, where an attacker makes use of a function with a printf style format string argument to perform an attack with results much like a buffer overflow, can be thwarted at runtime with ....
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, pages 125--136, 1992.
Testing C Programs for Buffer Overflow Vulnerabilities - Haugh (2002) (Correct)
....Similar experiments with X Window and MS Windows programs produced similar results[29, 16] This is relevant to security because a program that misbehaves when given random input will likely misbehave when given malicious input. 2.1. 4 Purify A tool called Purify, presented by Hastings and Joyce [22], can be used to detect many kinds of memory errors. This includes accessing a bu er past its bounds. Purify works by instrumenting the compiled program with code that performs di erent kinds 7 of memory bookkeeping. It would detect a bu er over ow attack, but due to the overhead of the ....
R. Hastings and B. Joyce. Purify: Fast Detection of Memory Leaks and Access Errors. In Proceedings of the Winter USENIX Conference, 1992.
Detecting Heap Smashing Attacks Through Fault Containment.. - Fetzer, Xiao (2001) (4 citations) (Correct)
....this approach does not require the recompilation of the source code. Our wrapper actually uses the same mechanism as Libsafe to confine stack smashing attacks. Therefore, we do not repeat the discussion in this paper. Unlike Libsafe, our wrapper also prevents heap smashing attacks. Purify [4] is a software debugging tool that detects memory faults and leaks. It inserts checking instructions for every memory access operation performed by the program. Purify provides comprehensive checking for memory access errors, not just for buffer overflows. In particular, it uses an adaptation of ....
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, 1992.
A Practical Flow-Sensitive and Context-Sensitive C and C++.. - Heine, Lam (2003) (5 citations) (Correct)
....Memory leaks can cause memoryintensive and long running programs, such as server codes, to fail. Deleting an object that has already been deleted can cause memory corruption. 1. 1 Existing Tools Dynamic tools like Purify are commonly used for detecting memory management errors in programs[20]. Purify instruments a program and reports all allocated memory at program exit that is not pointed to by any pointers. Unfortunately, it can only find leaks that occur during instrumented executions and incurs a nontrivial run time overhead. Moreover, Purify can only identify the allocation sites ....
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, pages 125--136, December 1992.
Fail-Safe ANSI-C Compiler: An Approach to Making C.. - Oiwa, Sekiguchi.. (2002) (5 citations) (Correct)
....as soon as the full implementation is completed. 5 Related Work There are many related research activities. They can be roughly classified into two categories. The focus of the first category is to detect various error states at runtime which are common to many programs. For example, Purify [5] and Sabar C (CodeCenter) 8] dynamically detect memory access errors caused by array boundary overflow. In addition, 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 ....
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proc. 1992 Winter USENIX Conference, pages 125--136, 1992.
Backwards-compatible bounds checking for arrays and pointers.. - Jones, Kelly (1997) (34 citations) (Correct)
....variables, virtual functions, and 7 7 call backs. 8 8 Maintain shadow bitmap: Maintain a map indicating which storage regions are valid. Update it when stack allocations, malloc and free occur. Augment each memory access instruction with code to check whether the address is valid [Hastings and Joyce, 1992]. Advantages: Fairly ecient Doesn t require access to source code, so can (must) be applied to all constituents of application False negatives fails to ag accesses to a valid region using an 9 9 improperly derived pointer 10 10 Summarise requirements: Track intended referent for each ....
Hastings, R. and Joyce, B. (1992). Purify: fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, pages 125-136.
Testing C Programs for Buffer Overflow Vulnerabilities - Haugh, Bishop (2003) (Correct)
....execution. Compilers can add code to check bounds or to arrange data structures in memory to cause hardware faults if bounds are exceeded; however, this additional instrumentation is often turned off in the name of efficiency. Various tools augment, or replace, this ability. For example, Purify [13] can detect many kinds of memory errors, including accessing a buffer past its bounds. To do so, it instrumentsg the compiled program with code that performs different kinds of memory bookkeeping. An alternate approach is to test programs. A tool called Fuzz was used to test standard UNIX ....
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, 1992.
Memory Management for High-Performance Applications - Berger (2002) (2 citations) (Correct)
....burden on the programmer to ensure that objects are freed by the correct memory manager. Custom memory managers also can make it difficult to understand the sources of memory consumption in a program. Using custom memory managers often precludes the use of memory leak detection tools like Purify [39]. However, custom memory managers can provide some important software engineering benefits. The use of region based custom memory managers in parsers and compilers (e.g. 176.gcc, lcc, and mudlle) simplifies memory management [38] Regions provide separate memory areas which a single call deletes ....
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX 1992.
Defining Software Visualizations Dynamically (Extended Abstract) - Reiss (Correct)
....Information gathering is done unobtrusively and automatically by the Desert environment. Facilities are currently provided here for collecting cross reference information from compiler output and approximate scanners and for obtaining dynamic information through the use of patching technology [8,10,11]. Access to this information is available through queries sent through the message server from other tools. The second component of our solution is to provide a wide range of visualization strategies. Previous experience indicated that abstract representations such as those provided by Seesoft ....
Reed Hastings and Bob Joyce, "Purify: fast detection of memory leaks and access errors," Proc. Winter Usenix Conf, (January 1992).
Enhancing Software Reliability with Speculative Threads - Oplinger, Lam (2002) (7 citations) (Correct)
....tampered with. Execution monitoring tools that help find memory management errors are widely used. For example, Purify monitors memory accesses to detect memory leaks, duplicate frees and illegal access errors such as reading past the end of heap allocated objects or from uninitialized memory[12]. While StackGuard and Purify are designed to find specific types of programming errors, DIDUCE is a more general tool that helps programmers find all kinds of application specific bugs[11] DIDUCE instruments Java bytecode to watch the data values accessed at various code points in the program. ....
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, December 1992.
ESP: A Language for Programmable Devices - Kumar (2002) (Correct)
....bugs are notoriously difficult to find because they usually result in memory corruption that leads to faulty behavior at a location in the program different from the site of the bug. A number of tools [104] help in detecting memory allocation in unsafe languages like C. For instance, the Purify [49] tool inserts code in the executable that check for a number of bugs like invalid indices in array accesses and memory leaks. This allows it to detect error when it happens at run time. However, it is the programmer s responsibility to run the executable with different inputs so as to exercise ....
R. Hastings and B. Joyce. Purify: Fast Detection of Memory Leaks and Access Errors. In Proceedings of the USENIX Winter Technical Conference, San Francisco, California, January 1992.
Simple and General Statistical Profiling with PCT - Charles Blake Steve (2002) (1 citation) (Correct)
....open source platforms. For instance, profiling instrumented libraries in usr lib on open source distributions are scarce or entirely absent. Also, it is possible to instrument code long after linking it. For example, binary rewriting techniques along the lines of Pixie [23] or Quantify [14] allow this. Completely dynamic instrumentation is also possible. 18] Nonetheless, instrumentation, at whatever time, raises several issues. Instrumented code really is not the same as the original code. Subtle microarchitectural e#ects can make it hard to understand the overhead of new ....
....basic blocks instead of function calls. Many implementations of these types of profiler are not robust to improper program exits and are not tolerant of inadequate data in some objects. Many systems have also implemented some form of link time instrumentation or post link time binary re writing. [23, 14, 9, 15, 24, 20] These address rebuilding issues somewhat and have some weak extensibility. A significant invasion of foreign code may remain, though. The code must be inserted to count executions, or, in more involved cases, log procedure arguments. Recently, a number of researchers have begun investigating the ....
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proc. of the Winter 1992.
Cut-based Functional Debugging for Programmable.. - Kirovski, Potkonjak.. (2000) (Correct)
.... While the precompilation choice requires in source code embedding of cut I O instructions (for example, used in the MIPS Pixie [26] the postprocessing step encompasses object code instrumentation similar to that implemented in Purify (Purify uses this technique to locate memory access errors) [11]. The precompilation approach has a significant advantage due to independence with respect to the hardware platform. Debugging platforms that can provide real time JTAG support for such an approach have been already developed and marketed. An example of instrumented code is given in Fig. 4 where ....
R. Hastings and B. Joyce, "Purify: Fast detection of memory leaks and access errors," USENIX, pp. 125--136, 1992.
Checking System Rules Using System-Specific.. - Engler, Chelf, Chou.. (2000) (5 citations) (Correct)
....effectiveness. At a lower level, the ATOM object code modification system [31] gives users the ability to modify object code in a clean, simple manner. By focusing on machine code, ATOM can be used in more situations than MC, which requires source code. However, while dynamic testing schemes [13, 30] are well served by object level modifications, it would be difficult to perform our static checks without the semantic information available in the compiler. Concurrently with our original work [9] Kiczales et al. 18] proposed aspect oriented programming (AOP) as a way of combining code that ....
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, December 1992.
Tracking Down Software Bugs Using Automatic Anomaly Detection - Hangal, Lam (2002) (54 citations) (Correct)
....online checking of invariants, in addition to detecting them. Keeping the space of dynamic invariants small allows us to scale our implementation to large programs and carry out the invariant analysis online, enabling rapid feedback to the user. Other dynamic bug detection techniques like Purify [10] and similar tools are widely used in commercial software development to detect unsafe programming practices like uninitialized memory reads, memory leaks and array bounds overruns. However, most of these errors are automatically avoided in a type safe, garbage collected language like Java. Eraser ....
R. Hastings and R. Joyce. Purify: Fast Detection of Memory Leaks and Access Errors. In Proceedings of the Winter Usenix Conf. pp. 125-136, January 1992.
Bell: Bit-Encoding Online Memory Leak Detection - Michael Bond Kathryn (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast Detection of Memory Leaks and Access Errors. In Winter USENIX Conference, pages 125--136, 1992.
EXE: A System for Automatically Generating Inputs of.. - Cadar, Twohey.. (2006) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, Dec. 1992.
Enhancing Software Reliability With Speculative Threads - And The Committee (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, December 1992.
JNuke: Efficient Dynamic Analysis for Java - Artho, Schuppan, Biere.. (2004) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proc. Winter USENIX Conf. (USENIX'92), 1992.
Advanced Unit Testing - How to Scale up a Unit Test Framework - Artho, Biere (2006) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proc. USENIX 1992.
Enhancing Security through Hardware-assisted Run-time .. - Arora, Raghunathan.. (2005) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proc. Winter USENIX Conf., pages 125--136, Jan. 1992.
An Efficient and Backwards-Compatible Transformation to.. - Xu, DuVarney, Sekar (2004) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, pages 125--136, 1992.
Low-Overhead Interactive Debugging via Dynamic.. - Marc Corliss Christopher (2005) (1 citation) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors in C and C++ programs. In Proc. of Winter 1992.
Caroline Mae Tice - Report No Ucb (Correct)
No context found.
Hastings, R., and Joyce, B., "Purify: Fast Detection of Memory Leaks and Access Errors", Proceedings of USENIX Winter 1992.
Buffer Overflow and Format String Overflow Vulnerabilities - Lhee, Chapin (2002) (Correct)
No context found.
Hastings R, Joyce B. Purify: Fast Detection of Memory Leaks and Access Errors. Proceedings of the Winter USENIX Conference USENIX: 1992.
An Efficient and Backwards-Compatible Transformation to.. - Xu, DuVarney, Sekar (2004) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, pages 125--136, 1992.
AccMon: Automatically Detecting Memory-related.. - Zhou, Liu, Fei.. (2004) (2 citations) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the USENIX Winter Technical Conference, 1992.
Code Inection in C and CPP: A Survey of Vulnerabilities.. - Younan, Joosen, Piessens (2004) (Correct)
No context found.
Reed Hastings and Bob Joyce. Purify: Fast Detection of Memory Leaks and Access Errors. In Proceedings of the Winter '92 USENIX conference, pages 125--136, San Francisco, California, U.S.A., January 1992. USENIX Association. (Cited on pages 27, 31 and 66.)
Reconsidering Custom Memory Allocation - Emery Berger Dept (2004) (1 citation) (Correct)
No context found.
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX 1992.
Enhancing Server Availability and Security through .. - Rinard, Cadar.. (2004) (3 citations) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, 1992.
iWatcher: Efficient Architectural Support for Software.. - Zhou, Qin, Liu, Zhou.. (2004) (1 citation) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Usenix Winter Technical Conference, January 1992.
Memory Management for High-Performance Applications - Berger (2002) (2 citations) (Correct)
No context found.
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX 1992.
Reconsidering Custom Memory Allocation - Berger, Zorn, McKinley (2002) (1 citation) (Correct)
No context found.
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX 1992.
JNuke: Efficient Dynamic Analysis for Java - Artho, Schuppan, Biere.. (2004) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proc. Winter USENIX Conf. (USENIX'92), 1992.
iWatcher: Efficient Architectural Support for Software.. - Zhou, Qin, Liu, Zhou.. (2004) (1 citation) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Usenix Winter Technical Conference, January 1992.
iWatcher: Efficient Architectural Support for Software Debugging - Pin Zhou Feng (2004) (1 citation) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Usenix Winter Technical Conference, January 1992.
Safe Programming at the C Level of Abstraction - Grossman (2003) (Correct)
No context found.
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Winter USENIX Conference, pages 125--138, San Francisco, CA, January 1992.
Taming C Pointers - Necula, McPeak, Weimer (2002) (Correct)
No context found.
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Usenix Winter 1992 Technical Conference, pages 125--138, Berkeley, CA, USA, January 1991. Usenix Association.
CCured: Type-Safe Retrofitting of Legacy Code - Necula, McPeak, Weimer (2002) (63 citations) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Usenix Winter 1992.
CCured in the Real World - Jeremy Condit Matthew (2003) (13 citations) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Usenix Winter 1992.
Flashback: A Lightweight Extension for Rollback and .. - Srinivasan.. (2004) (1 citation) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In the Winter USENIX, 1992.
JNuke: Efficient Dynamic Analysis for Java - Artho, Schuppan, Biere.. (2004) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proc. Winter USENIX Conf. (USENIX'92), 1992.
High Performance Robust Computer Systems - DeVale (2001) (1 citation) (Correct)
No context found.
Hastings, R.; Joyce, B., "Purify: fast detection of memory leaks and access errors," Proceedings of the Winter 1992 USENIX Conference
ARCHER: Using Symbolic, Path-sensitive Analysis to Detect.. - Xie, Chou, Engler (2003) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Winter USENIX Conference, December 1992.
iWatcher: Efficient Architectural Support for Software.. - Zhou, Qin, Liu, Zhou.. (2004) (1 citation) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Usenix Winter Technical Conference, January 1992.
Compiler-Directed Run-Time Monitoring of Program Data Access - Chen Ding Yutao (2002) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: fast detection of memory leaks and access errors. In Proceedings of the Winter Usenix Conference, 1992.
CCured in the Real World - Condit, Harren, McPeak, Necula.. (2003) (13 citations) (Correct)
No context found.
R. Hastings and B. Joyce. Purify: Fast detection of memory leaks and access errors. In Proceedings of the Usenix Winter 1992.
Vmalloc: A General and Efficient Memory Allocator - Vo (1996) (17 citations) (Correct)
No context found.
R. Hastings and R. Joyce. Purify: Fast Detection of Memory Leaks and Access Errors. In Proceedings of the Winter 1992.
JiTI: Tracing Memory References for Data Race Detection - Ronsse, De Bosschere (1997) (1 citation) (Correct)
No context found.
Reed Hastings and Bob Joyce. Purify: Fast detection of memory leaks and access errors. Proceedings of the Winter USENIX Conference, pages 125--136, January 1992.
First 50 documents Next 50
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