Re: Suggestions for C malloc debugging tool

Joerg Schoen writes:
|> [ suggest instrumenting C source with pointer validity checking code]


Harish Patil <patil@ch.hp.com> writes:
|> As part of my Ph.D. thesis at UW-Madison I had developed such a C to C
|> translator for pointer and array access checking using a technique
|> called "guarding". I had also done a detailed comparison of our
|> translator with "Purify". A paper based on "guarding" appears in this
|> month's `Software -- Practice and Experience'.


An earlier attempt at a similar tool (although not as capable or robust
as Harish's design) is described in:


@ARTICLE{Austin:94,
    author = "T. M. Austin and S. E. Breach and G. S. Sohi",
    title = "Efficient Detection of All Pointer and Array Access
                                    Errors",
    journal = "Proceedings of the {ACM} {SIGPLAN} '94 Conference on
                                    Programming Language Design and Implementation",
    year = 1994,
    volume = 30,
    number = 6,
    pages = "",
    month = jun
}


Regards, -Todd
--
%% Todd Austin, taustin@ichips.intel.com
%% MicroComputer Research Labs, Intel Corporation, Hillsboro, Oregon
--

Return to the comp.compilers page.
Search the comp.compilers archives again.