Interesting... if you're so tight on memory that you can't even load spin,
I'd say you have a bigger problem. It only needs about 128k ... Not having
that much essentially means you can't run many other utilities, because
shell won't be able to fork (unless you use some smaller shell, but even
then most utilities will require at least half as much).

You can modify the code to look only for certain pid instead of going
through all processes. Or just decrease the constant that defines max.
number of processes - the size of arrays used to keep & sort stuff depends
on it.

Interesting... if you're so tight on memory that you can't even load spin,
I'd say you have a bigger problem. It only needs about 128k ... Not having
that much essentially means you can't run many other utilities, because
shell won't be able to fork (unless you use some smaller shell, but even
then most utilities will require at least half as much).

You can modify the code to look only for certain pid instead of going
through all processes. Or just decrease the constant that defines max.
number of processes - the size of arrays used to keep & sort stuff depends
on it.

-- igor

"Janusz Ruszel" <janusz_ruszel@notvalid.com> wrote in message
news:bth93c$36a$1@inn.qnx.com...
There is no space to run "spin" on the target I want to debug for memory
leaking. Yeah, I can run it remotly. Spin is a great tool but I need
check
heap size inside my application.

The description of malloc_g library says that there is function to check
the
heap size but the function itself is not implemented.

Janusz Ruszel.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:btgdvq$d3s$1@inn.qnx.com...
You might find "spin" (included on 3rd party CD) more useful for this
purpose.

Igor,
where I can find spin source code? Did you use "electrict fance" ?
(any thoughts to share? )

Thanks,
Janusz.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:bthcc1$58k$1@inn.qnx.com...
Interesting... if you're so tight on memory that you can't even load
spin,
I'd say you have a bigger problem. It only needs about 128k ... Not
having
that much essentially means you can't run many other utilities, because
shell won't be able to fork (unless you use some smaller shell, but even
then most utilities will require at least half as much).

You can modify the code to look only for certain pid instead of going
through all processes. Or just decrease the constant that defines max.
number of processes - the size of arrays used to keep & sort stuff
depends
on it.

-- igor

"Janusz Ruszel" <janusz_ruszel@notvalid.com> wrote in message
news:bth93c$36a$1@inn.qnx.com...
There is no space to run "spin" on the target I want to debug for
memory
leaking. Yeah, I can run it remotly. Spin is a great tool but I need
check
heap size inside my application.

The description of malloc_g library says that there is function to
check
the
heap size but the function itself is not implemented.

Janusz Ruszel.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:btgdvq$d3s$1@inn.qnx.com...
You might find "spin" (included on 3rd party CD) more useful for
this
purpose.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:bthcc1$58k$1@inn.qnx.com...
Interesting... if you're so tight on memory that you can't even load
spin,
I'd say you have a bigger problem. It only needs about 128k ... Not
having
that much essentially means you can't run many other utilities,
because
shell won't be able to fork (unless you use some smaller shell, but
even
then most utilities will require at least half as much).

You can modify the code to look only for certain pid instead of going
through all processes. Or just decrease the constant that defines max.
number of processes - the size of arrays used to keep & sort stuff
depends
on it.

-- igor

"Janusz Ruszel" <janusz_ruszel@notvalid.com> wrote in message
news:bth93c$36a$1@inn.qnx.com...
There is no space to run "spin" on the target I want to debug for
memory
leaking. Yeah, I can run it remotly. Spin is a great tool but I need
check
heap size inside my application.

The description of malloc_g library says that there is function to
check
the
heap size but the function itself is not implemented.

Janusz Ruszel.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:btgdvq$d3s$1@inn.qnx.com...
You might find "spin" (included on 3rd party CD) more useful for
this
purpose.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:bthcc1$58k$1@inn.qnx.com...
Interesting... if you're so tight on memory that you can't even load
spin,
I'd say you have a bigger problem. It only needs about 128k ... Not
having
that much essentially means you can't run many other utilities,
because
shell won't be able to fork (unless you use some smaller shell, but
even
then most utilities will require at least half as much).

You can modify the code to look only for certain pid instead of
going
through all processes. Or just decrease the constant that defines
max.
number of processes - the size of arrays used to keep & sort stuff
depends
on it.

-- igor

"Janusz Ruszel" <janusz_ruszel@notvalid.com> wrote in message
news:bth93c$36a$1@inn.qnx.com...
There is no space to run "spin" on the target I want to debug for
memory
leaking. Yeah, I can run it remotly. Spin is a great tool but I
need
check
heap size inside my application.

The description of malloc_g library says that there is function to
check
the
heap size but the function itself is not implemented.

Janusz Ruszel.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:btgdvq$d3s$1@inn.qnx.com...
You might find "spin" (included on 3rd party CD) more useful for
this
purpose.