[bf1942] Another new build...

[Stefan Leuenberger]

Was running more stable than ever... crashed after about 1 hour:

(gdb) info stack
#0  0x9135654 in _STL::basic_ostringstream<char,  
_STL::char_traits<char>, _STL::allocator<char> >::~basic_ostringstream  
()
Cannot access memory at address 0xbfbfeba0.

Thanks Ryan, you code machine!

On Sonntag, Dezember 15, 2002, at 08:26  Uhr, Ryan C. Gordon wrote:

>
> Try this one on for size:
>    
> http://icculus.org/betas/bf1942/bf1942-lnxded-betaupdate-build- 
> 1039933525.tar.bz2
>
> This applies over the complete install, with or without the previous
> build. Just untar it so it overwrites the binaries and README.
>
> I fixed a metric ton of invalid memory accesses, three deferences of  
> bogus
> pointers, and one serious memory corruption (which I'm hoping was the
> cause of all our woes).
>
> Please try it out. Usual disclaimer applies: this works great here  
> (but it
> always has, so this is not at all a comfort by this point, I'm sure),  
> but
> until I get some confirmation from the field, I can't promise this  
> won't
> crash on connect, etc.
>
> And, for the record, valgrind is a _fantastic_ tool for tracking down
> memory bugs. If you are a programmer and aren't using this on your  
> code,
> you really really should. It totally blows away ElectricFence (which,
> coincidentally, runs out of mmap()able address space before the server  
> is
> finished starting...I've had that problem with efence on every major  
> game
> I've used it with), and dmalloc, etc.
>
> --ryan.
>
>
>