Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

memPartAlloc: block too big

2,711 views
Skip to first unread message

Katarina

unread,
Jan 8, 1999, 3:00:00 AM1/8/99
to
Hello!

I've made a xWorks program, running on a VME2604 card. It uses TCP/IP to
communicate with a UNIX-machine.

The problem is that when I let the programs run for a while I get the error:
0x1be1ff0 (Re ): memPartAlloc: block too big - 10512 in partition 0x184d20.
0x1be5418 (FromIO0): memPartAlloc: block too big - 10512 in partition
0x184d20.

Where should I look for the problem? I've tried everything I can think of.
I'm working in the Tornado shell. So the VxWorks sorroundings are loaded at
start up, and then I load my own part by hand.

I can't find where the error meassage is written, and not why.

Please, give me an idea!

Katarina

Chris Varlese

unread,
Jan 8, 1999, 3:00:00 AM1/8/99
to
It could be a memory leak. Use the 'memShow' function in the
shell to watch the free memory level.

It could be heap fragmentation. Use memShow to see what is
the largest free block. Are you making lots of little objects?

It could be a corruption of the heap. If you write past the
end of a malloc'ed block you may damage the heap structure and
that may result in some strange heap errors.

regards,

Chris Varlese

Lawrence T. Hoff

unread,
Jan 8, 1999, 3:00:00 AM1/8/99
to

It sounds like you have a "memory leak". I.e. some portion
of your application is allocating memory, but not freeing it.
Eventually there is no more memory to allocate.

Read the "memLib" documentation. See how memShow can be
used to monitor memory usage.

You may wish to buy RTIlib from http://www.rti.com to help
track down the cause of the memory leak.

HTH -- Larry


--
Building 911-C, Brookhaven National Laboratory
PO Box 5000, Upton, NY, 11973
http://www.rhichome.bnl.gov/~hoff, mailto:ho...@bnl.gov
Phone: (516) 344-2194 FAX: (516) 344-5443

Katarina

unread,
Jan 11, 1999, 3:00:00 AM1/11/99
to
Hello again!

I've tried memShow. It says that current free and alloc memory don't
changed, but cumulative alloc keeps getting higher.

But it seems this number keeps raising just by calling a function?! Is it an
error that this raise? Any ideas what I could do about it in that case?

I don't have any alloc or malloc in my program.

Katarina

Stephen A Walsh

unread,
Jan 11, 1999, 3:00:00 AM1/11/99
to

Have you tried looking at Stack Usage.

Most occurances I have had with the above message is running out of
stack space.


Hope This Helps,


Steve
--

*******************************************
Stephen A Walsh
Senior Software Engineer
Radar and Countermeasures Systems
Marconi Electronic Systems
*******************************************
Opinions are usually mine and mine alone
*******************************************

0 new messages