|
From: Robert W. <rj...@du...> - 2005-05-30 21:30:46
|
On Mon, 2005-05-30 at 14:41 -0500, Nicholas Nethercote wrote: > On Mon, 30 May 2005, Robert Walsh wrote: >=20 > > * id =3D VALGRIND_STACK_NEW(start, end) registers the memory betwe= en > > start and end as a new stack and returns an id you can use for > > the other client requests described below. This doesn't > > allocate memory or anything - it just records that a particular > > memory range is a stack. > > > > * VALGRIND_STACK_DELETE(id) removes the stack association for > > stack "id". This doesn't free memory or anything - it just > > tells Valgrind that the piece of memory register earlier is no > > longer a stack. >=20 > Perhaps VALGRIND_STACK_REGISTER and VALGRIND_STACK_DEREGISTER would be=20 > better names? You'd avoid the confusion with memory allocation. Yes. I'll do that. Regards, Robert. --=20 Robert Walsh Amalgamated Durables, Inc. - "We don't make the things you buy." Email: rj...@du... |