Ion Gaztañaga wrote:

...

I can't seem to get the hang of strings though. I've looked around online and can't seem to find an example of how this should be set up, and I can't get it to accept an allocator. The only way I can seem to typedef one is something like:

typedef boost::interprocess::string BoostString - or - typedef boost::interprocess::basic_string<char> BoostString;

so defint it like this:

using namespace boost::interprocess; typedef basic_string shm_string;

As with vector, you will need to pass an allocator to the string cosntructor. See also string_test.cpp test in boost/libs/interprocess/test for an example of shared memory strings.

I'm still having a little trouble. The allocator they use in string_test.cpp is one totally implemented there for that project; I'm not going to have to do / copy that am I? I've tried: typedef boost::interprocess::basic_string BoostString; AND: typedef boost::interprocess::allocator CharAllocator; typedef boost::interprocess::basic_string BoostString; Neither of these bite, I get compiling errors... "allocator_type" doesn't work / isn't defined (even with boost::interprocess qualifier). Am I missing something? -- View this message in context: http://old.nabble.com/Boost%3A%3Ainterprocess%3A%3Astring-problems-tp2920612... Sent from the Boost - Users mailing list archive at Nabble.com.

On 26/07/2010 20:00, this_thread wrote:

Correction, I was forgetting:

const CharAllocator *charAllocator = new CharAllocator(m_pShMem.get_segment_manager()); m_foostring = m_pShMem.construct<BoostString>("m_foostring")(*charAllocator);

It compiles now, but I'm getting weird errors during run time that I'm having trouble tracking down:

terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct NULL not valid Aborted (core dumped)

You are assigning or constructing a string from a null pointer. I think interprocess is ok, now it's in your hands ;-) Best, Ion

this_thread wrote:

I think interprocess is okay too. ;) I'm confused about the null pointer though.. I've printed out m_pShMem, charAllocator, they're both okay... and it's crashing somewhere in between that initialization and the one call I have that actually uses a BoostString.

This would be a lot easier if interprocess containers didn't equate to madness in gdb...

Yeah, this is odd... it's crashing on a function call with the definition: bool function(std::string, unsigned int, std::string, int, int, int, int, ErrorCode&); I try to step into the function and it raises a SIGABRT. Don't even get anywhere. Very odd... -- View this message in context: http://old.nabble.com/Boost%3A%3Ainterprocess%3A%3Astring-problems-tp2920612... Sent from the Boost - Users mailing list archive at Nabble.com.