> > and the data that we referenced was not there anymore. It
> was a
> > case of bad code, worked under 95, but did not under NT.
> > </noflame>
>
> If this is the way all windows programs are written, the I
> don't have any
> questions any more.
the point that I was tryiing to make was that different OS's
handle memory differenly, and even similar OSes (winxx) handle
memory differently.
The original question was asked why does his program crash under
one OS (Linux) and work under another (unmentionable on this
list it seems) when all he was doing was a malloc and free's?
My explaination pointed out how the OS'es handle memory
differently and that it was my experience that we had to look in
OUR source code to fix the problem when dealing with cross
platform programming. My subtle suggestion that was over looked
it seems by ALL was that maybe he needs to look in HIS source
code and try to fine tune it rather than look for a new OS that
would run it. Also if it is spawning that many threads he may
want to consider a distributed processing enviroment like a
cluster.
Something else that may have been overlooked is that he may have
spawned more threads then his sytem was set up to handle under
Linux. As I can do a make -j 300 on my system but any more
process than that will crash it. And yes I do know that the
number of processes can be increased, but I have no need for
that. Even a make -j 300 will not spawn all 300 process on my
system. This may possibly be the reason his system is crashing.
Lastly I have left this list so please stop mailing me and
cc'ing me.
_________________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
