New Updater doesn't work

[peeg]

Greetings!
I\'v reinstalled PS using the 0.13-full-package and have no problems to play on Laanx, seeing all the new eyecandy.
I have some strange graphic bugs ( I can see through Klyros, diappearing trees on ojaroad .. ) and thought it would be a good idea to run the new updater.
That doesn\'t work.  
Here\'s my shell output:

Code: [Select]


peg@Caldera:/mnt/hdb1/games/planeshift$ ./updater --auto
Critical files () not found (Server only)
NOTIFY: psUpdaterEngine initialized.
Checking registry version...
Server error 404 (http://psmirror.u24.solone.net/psupdater/version.dat)
Couldn\'t connect to mirror mir4!
Trying mirror mir1..
Server error 301 (http://psmirror.pfdev.net/psupdater/version.dat)
Bad version info in file: /this/updatertemp/mir1.dat
*** glibc detected *** free(): invalid pointer: 0x085b7f74 ***
Aborted

Any ideas?

[Xordan]

It\'s a known problem, for all platforms. We hope to fix it soon.

[DaveG]

The update servers have been updated, and should work now.  There seems to be another problem here.

Edited to add:
We found the problem.  It\'s fixed in CVS right now (though, may not be on annon yet) and will be put in the next package.

[StarsAndBars_1018]

I\'m having that problem at the moment too. So, its good that its been fixed.

PS @Xordan: I like the signature banner.

[Monteaup]

Same to me. I can\'t update...

[Monteaup]

There is already a Post about it.

As root...

export MALLOC_CHECK_=0


then it works !

[rakshak]

I used the export command in the above post as root. Here is the result:

akumar@rakshak:~/planeshift$ ./updater
Opening GLX2D
Creating Context
Video driver GL/X version (direct renderer)
Visual ID: 0x00000023, 16bit TrueColor
R5:G6:B5:A0,
level 0, double buffered
NOTIFY: Applied: Mesa DRI: Force upload of precompressed DXT textures
NOTIFY: OpenGL renderer: Mesa DRI Intel(R) 915GM 20050225 (vendor: Tungsten Graphics, Inc) version 1.3 Mesa 6.4.1
NOTIFY: Using windowed mode at resolution 640x480.
NOTIFY: Pixel format: Color: 16 Alpha: 0 Depth: 16 Stencil: 0 AccumColor: 0 AccumAlpha: 0 MultiSamples: 0
WARNING! Crystal Space performs better in 24 or 32 bit display mode!
NOTIFY: Multisample: disabled
Critical files () not found (Server only)
Mounting skin: /planeshift/art/apps.zip
Skipping \'YesNo\' because it\'s already loaded
NOTIFY: psUpdaterEngine initialized.
Server error 301 (http://psmirror.pfdev.net/psupdater/version.dat)
*** glibc detected *** free(): invalid pointer: 0x7220282c ***
Aborted


So the problem still remains!!!
(I am using Ubuntu Dapper on Dell Inspiron 6000 without ATI or nVidia

[Induane]

try



export MALLOC_CHECK_=0 && ./updater -auto

[Wanchu]

It does work for me if I do this in a console:

export MALLOC_CHECK_=0

/updater -auto

You MUST run the updater in the same console where you did that export, because when you close the console, that variable is lost. You have to do that export every time you want to run the updater in a console. I would do the -auto thing, in order to avoid problems with the graphical interface.

I have only tried as a normal user, NOT as root.

I hope this helps.

P.D.- I also have to do that export before I run PlaneShift client on any console (and I must do the export ON THE SAME console I want to run the PlaneShift client on).

[Induane]

I have little scripts that I run to start planeshift anyways - they set environment variables, and a few other little things - I like to renice it to +19 as I consistantly get an extra 5 fps out of that.  So I just added the export MALLOC_CHECK_=0 to each script.  That way it is taken care of.

[Wanchu]

With the temporary solution for the 0.3.014 written by Bereror ( http://planeshift.oodlz.com/wbboard/thread.php?threadid=22947&boardid=41&styleid=3&sid=e3f21623fc9c26d5939932b139aa137a ) there is no need to do the \"export MALLOC_CHECK_=0\".

In the #planeshift-build channel in IRC they have told me that the \"export MALLOC_CHECK_=0\" will not be needed in the final version of the 0.3.014 .

[DaveG]

It\'s not even needed if you built 0.3.013 from the 6th of March.

[Wanchu]

Could someone explain what is the effect of exporting that variable with that value? I am a newbie in Linux and would thank to learn a little. Just answer this if you have free time and feel like answering, its not needed to make my game work

Thank you

[Bereror]

Here is the long description how and why the MALLOC_CHECK_ variable is used:

Heap Consistency Checking

It is used to detect memory allocation errors. Like in the following simple example:

Code: [Select]


int main(void)
{
  char *buf;

  /* Allocate memory */
  buf = malloc(100);

  /* Release memory */
  free(buf);

  /* Did I release memory? Ok, release it once more */
  free(buf);

  return 0;
}


The second free() is actually invalid, but with MALLOC_CHECK_=0 it would be silently ignored.