To check whether a failure so early within the function might be related to
some illegal args coming down from MemoryObject::newSegment, I compiled with
CXXFLAGS="-DMEMPROFILE" cmake -DBUILD_DEB=1 -DCMAKE_BUILD_TYPE=RELEASE
~/oorexxsvn/main/trunk
to enable the #ifdef MEMPROFILE sections we have
With that, running unoptimized rexximage without exception will print
Allocating a new segment of 524256 bytes
Allocating boundary a new segment of 1048576 bytes
Allocating a new segment of 1048576 bytes
Allocating boundary a new segment of 2097152 bytes
Allocating a new segment of 33554400 bytes
Allocating boundary a new segment of 33554432 bytes
Allocating large boundary new segment of 4194304 bytes for request of
4194272
Object stats for this image save are
ObjectTypeNum Total Objects TotalBytes
============= ============== ==========
0 0 0
1 1 144
2 36 5184
.. and a long list until..
184 0 0
185 0 0
running optimized rexximage will fail like this:
Allocating a new segment of 524256 bytes
Allocating boundary a new segment of 1048576 bytes
Segmentation fault (core dumped)
So the failure seems to occur, when this code path is run for the first
time:
// try to allocate a new segment
MemorySegment *segment = currentPool->newSegment(requestedBytes);
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
