[nonhuman]

For some reason when I try to declare an array of 234,936 strings in C++ on OS X I get a seg fault. When i do it in Linux it works fine. Why is it doing this? Is there some way I can tell OS X not to?

[kamprath]

Originally posted by nonhuman:
<STRONG>For some reason when I try to declare an array of 234,936 strings in C++ on OS X I get a seg fault. When i do it in Linux it works fine. Why is it doing this? Is there some way I can tell OS X not to?</STRONG>

Are you declaring the array on the stack? If so, that's why. I'm surprised Linux survived it too (though I am not too familitar with the details fo Linux). Always create very large memory blocks dynamically (using new). Then check for the allocation's success by ensuring your pointer is not NULL.

Michael Kamprath

[nonhuman]

Ok, thanks. I'll try that out.

[Angus_D]

Either that or change the size of the stack limitation (ulimit stack, for example).

[nonhuman]

Ok, stupid question: How do you declare an array dynamically? Is it
<BLOCKQUOTE><font size="1"face="Geneva, Verdana, Arial">code:</font><HR><pre><font size=1 face=courier>string* dictionary = new string[size]</font>[/code] or <BLOCKQUOTE><font size="1"face="Geneva, Verdana, Arial">code:</font><HR><pre><font size=1 face=courier>string* dictionary[size] = new string</font>[/code] or what?

[aleph_null]

string* dictionary = new string[size];

did that not work?

if you don't have to use a bare array (if this isn't homework or something), i'd suggest an stl container. std::vector or some such. they're really easy to use once you get the hang of them.

oh, and std::string, of course, is an stil container... is that what you're using?