使用Purify检查内存泄漏
3星 · 超过75%的资源 需积分: 50 148 浏览量
2016-01-03
13:03:01
上传
评论 1
收藏 1.42MB PDF 举报 
Purify:
Fast
Detection
of
Memory
Leaks
and
Access
Errors
Reed
Hastings
and
Bob Joyce
Pure Sofware
Inc.
Abstract
This
paper
describes
Purifyru,
a software
testing
and
quality
assurance
Ool
that
detects
memory
leaks and access
erors.
Purify
inserts
additional
checking
instructions directly
into the
object
code
produced
by
existing
compilers.
These
instructions
check every
memory
read and
write
performed
by
the
program-under-test and
detect several
types
of
access
errors,
such
as
reading
uninitialized
memory
or witing
to
freed
memory.
Purify
inserts checking
logic
into all of
the code
in
a
program, including third-party
and
vendor
object-code
libraries, and
verifies system
call
interfaces.
In addition,
Purify
tracks
memory
usage
and
identifies
individual
memory
leals using a
novel adaptation
of
garbage
collection
techniques.
Purify
produces
standard
executable
files compatible
with existing
debuggers,
and
currently
runs on
Sun
Microsystems'
SPARC
family
of
workstations.
Purify's
neafly-comprehensive
memory
access
checking
slows
the target
program
down
typically
by
less than a
facor of
three
and
has
resulted
in
significantly
more
reliable
software
for
several
development
goups.
L.
Introduction
A single
memory
access
error,
such as
reading
from
uninitialized
memory or
writing to
freed
memory can cause
a
progam to act unpredicAbly
or
even
crash.
Yet,
it is nearly
impossible
to eliminate
all such
errors
from a
non-trivial
progam
For one
thing, these
erors
may
produce
observable
effects
infrequently
and
intermittently.
Even
when
p-gru.r are tested
intensively
for extended
periods,
errors
can and
do escape
detection.
The
unique
combination
of
litco*stanos
required
for an
error to
occur and
for
its symptoms
lo becomc
visible
may
be
virtually
impossible to
create
in the development
or
test environment.
As
a
result,
proglammers
spend
much time
looking
for these
errors,
but
end-users
may experience
tlem
first.
[Miller90]
empirically
shows
the continuing
prevalence
of access errors
in
many
widely-used
Unix
Programs.
Even
when
a
memory
access
error triggers
an
observable
symptom,
the
error can take
days to
nack down
and
eliminate.
This
is
due
to the
frequently
delayed and
coincidental
connection
between
the cause,
typically
a
memory
comrption,
and
the symptom,
typically
a crash
upon
the
eventual
reading
of
invalid data.
Mennry
leaks,
rhat
is,
memory allocated
but
no longer accessible
to
the
program,
slow
program
execution
by
increasing
paging,
and
can cause
progams
to
run out
of
memory.
Memory
leaks
are
more
difficult
to detect than
illegal
memory
accesses.
Memory
leaks
occur
because
a block
of
memory
was not
freed, and
hence are errors
of
omission,
rather than
commission.
In
addition,
memory
leaks
rarely
produce
directly
observable
elrors,
but
instead
cumulatively
degrade
overall
performance.
USENIX
-Winter
'92
125
剩余11页未读，继续阅读
资源评论
drfxiaoliuzi2018-08-08已经过时了的资源，现在已经用不了了
