Custom Allocator Question - Advanced.

[joe]

I have written a custom std allocator which follows the example in
Stroustrup's book.

I'm seeing a behavior I don't understand.

My allocate method within the allocator looks like the following:
(FooAllocator<T >)

pointer allocate(size_t ype cnt, typename
std::allocator< void>::const_po inter hint = 0)
{
pointer p = reinterpret_cas t<pointer(new char[sizeof(T)*cnt]);
std::cout<<"MEM ORY ADDRESS: "<<p<<std::endl ; //FIRST PRINT-OUT!
return p;
}

Then I have a regular container in my main:
int main()
{
typedef std::multiset<F oo,less<Foo>,Fo oAllocator<Foo MYSET;

MYSET mine;

MYSET::iterator iter = mine.insert(Foo ());
std::cout<<"ITE R = "<<&(*iter)<<st d::endl;
}

The address of the iterator being returned is 16 Bytes graeter than
the address of the allocated memory. This is true in multiple
compilers, and is causing me to overwrite the end of my allocated
memory. It doesn't seem to matter what type of object Foo is.

has anyone seen this before or have any ideas?
Thanks,
Joe

[Fei Liu]

joe wrote:

I have written a custom std allocator which follows the example in
Stroustrup's book.

I'm seeing a behavior I don't understand.

My allocate method within the allocator looks like the following:
(FooAllocator<T >)

pointer allocate(size_t ype cnt, typename
std::allocator< void>::const_po inter hint = 0)
{
pointer p = reinterpret_cas t<pointer(new char[sizeof(T)*cnt]);

This is probably the cause of your problem. reinterpret_cas t is not a
safe cast and it does not guarantee proper object alignment.

F

std::cout<<"MEM ORY ADDRESS: "<<p<<std::endl ; //FIRST PRINT-OUT!
return p;
}

Then I have a regular container in my main:
int main()
{
typedef std::multiset<F oo,less<Foo>,Fo oAllocator<Foo MYSET;

MYSET mine;

MYSET::iterator iter = mine.insert(Foo ());
std::cout<<"ITE R = "<<&(*iter)<<st d::endl;
}

The address of the iterator being returned is 16 Bytes graeter than
the address of the allocated memory. This is true in multiple
compilers, and is causing me to overwrite the end of my allocated
memory. It doesn't seem to matter what type of object Foo is.

has anyone seen this before or have any ideas?
Thanks,
Joe

[Charles Bailey]

joe wrote:

pointer allocate(size_t ype cnt, typename
std::allocator< void>::const_po inter hint = 0)
{
pointer p = reinterpret_cas t<pointer(new char[sizeof(T)*cnt]);
std::cout<<"MEM ORY ADDRESS: "<<p<<std::endl ; //FIRST PRINT-OUT!
return p;
}

Just for fun change the log message to this:
std::cout <<"MEMORY ADDRESS: " << p << ", sizeof T is"
<< sizeof(T) << std::endl;

Then I have a regular container in my main:
int main()
{
typedef std::multiset<F oo,less<Foo>,Fo oAllocator<Foo MYSET;

MYSET mine;

MYSET::iterator iter = mine.insert(Foo ());
std::cout<<"ITE R = "<<&(*iter)<<st d::endl;
}

The address of the iterator being returned is 16 Bytes graeter than
the address of the allocated memory. This is true in multiple
compilers, and is causing me to overwrite the end of my allocated
memory. It doesn't seem to matter what type of object Foo is.

&(*iter) is not the address of the iterator, it's the address of the
object "pointed" to by the iterator. As you can see, the object has a
different address to one you returned from the allocate call. This may
be because the instance of the allocator template that is being used is
probably not the one you think is being used.

Presumably you had to define a rebind struct, can you see what has happened?

If not, add some logging to your constructors, especially the templated one.
template<class UFooAllocator(c onst FooAllocator<U> &)

Charles.

[James Kanze]

On May 23, 9:46 pm, joe <joeyc...@mail. comwrote:

I have written a custom std allocator which follows the example in
Stroustrup's book.

I'm seeing a behavior I don't understand.

My allocate method within the allocator looks like the following:
(FooAllocator<T >)

pointer allocate(size_t ype cnt, typename
std::allocator< void>::const_po inter hint = 0)
{
pointer p = reinterpret_cas t<pointer(new char[sizeof(T)*cnt]);
std::cout<<"MEM ORY ADDRESS: "<<p<<std::endl ; //FIRST PRINT-OUT!
return p;
}

Then I have a regular container in my main:
int main()
{
typedef std::multiset<F oo,less<Foo>,Fo oAllocator<Foo MYSET;

MYSET mine;

MYSET::iterator iter = mine.insert(Foo ());
std::cout<<"ITE R = "<<&(*iter)<<st d::endl;
}

The address of the iterator being returned is 16 Bytes graeter than
the address of the allocated memory. This is true in multiple
compilers, and is causing me to overwrite the end of my allocated
memory. It doesn't seem to matter what type of object Foo is.

Presumably (I don't see how one could implement it differently),
what is being allocated in the multiset is not a T, but some
sort of node structure containing a T, typically with a couple
of pointers before the T. And the actual type of the allocator
being used to do the allocation should not be T, but this node
type.

Having said this, I don't quite see how this could be causing
you to overwrite anything. The allocation expression should be
something like (typedef's expanded, etc.):

__Alloc::rebind <__Node>::other ( myAlloc ).allocate( n )

If you're rebind declaration is correct, and the code for
allocate is really what you show, then you should have no
trouble in this respect; if you're not sure, add output of
typeid(T).name and sizeof(T) to your allocator, to see what is
going on.

--
James Kanze (GABI Software) email:ja******* **@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientier ter Datenverarbeitu ng
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]