hi,
i ran a soldatserver on a fedora core4 but since (i tought) i update the kernel to 2.6.16, i have this message displayed on my screen each time i launch the server

#./soldatserver
Runtime error 230 at 08059111
segmentation error

I found on the forum a thread talking about that...
any idea to solve the problem?
thx!

I was just having this problem on my new 64 bit system. Is this 64 bit that you're trying to run it on?

no just a normal 32bit

EDIT: i dont know if it could help someone, but i ran valgrind on the linux server and here is the log...

==10859== My PID = 10859, parent PID = 10646. Prog and args are:
==10859== ./soldatserver
==10859==
==10859== Valgrind library directory: /usr/lib/valgrind
==10859== Command line
==10859== ./soldatserver
==10859== Startup, with flags:
==10859== -v
==10859== --log-file=soldatlogmem.log
==10859== Contents of /proc/version:
==10859== Linux version 2.6.16-1.2108_FC4 (bhcole@h.redhat.com) (gcc version 4.0.2 20051125 (Red Hat 4.0.2-8)) #1 Thu May 4 23:52:01 EDT 2006
==10859== Reading syms from /data/soldatserver249/soldatserver (0x8048000)
==10859== object doesn't have a symbol table
==10859== object doesn't have any debug info
==10859== Reading syms from /lib/ld-2.3.6.so (0x1B8E4000)
==10859== object doesn't have any debug info
==10859== Reading syms from /usr/lib/valgrind/stage2 (0xB0000000)
==10859== Reading syms from /lib/ld-2.3.6.so (0xB1000000)
==10859== object doesn't have any debug info
==10859== Reading syms from /usr/lib/valgrind/vgskin_memcheck.so (0xB7C25000)
==10859== Reading syms from /lib/libc-2.3.6.so (0xB7E85000)
==10859== object doesn't have any debug info
==10859== Reading syms from /lib/libdl-2.3.6.so (0xB7FAF000)
==10859== object doesn't have any debug info
==10859== Reading suppressions file: /usr/lib/valgrind/default.supp
==10859==
==10859== Reading syms from /usr/lib/valgrind/vg_inject.so (0x1B901000)
==10859== Reading syms from /usr/lib/valgrind/vgpreload_memcheck.so (0x1B906000)
==10859== Reading syms from /lib/libNoVersion-2.3.6.so (0x1B90D000)
==10859== object doesn't have any debug info
==10859== Reading syms from /lib/obsolete/linuxthreads/libpthread-0.10.so (0x1B918000)
==10859== object doesn't have any debug info
==10859== Reading syms from /lib/libdl-2.3.6.so (0x46B000)
==10859== object doesn't have any debug info
==10859== Reading syms from /lib/obsolete/linuxthreads/libc-2.3.6.so (0x1B96C000)
==10859== object doesn't have any debug info
==10859== Conditional jump or move depends on uninitialised value(s)
==10859== at 0x1B9D6B77: strstr (in /lib/obsolete/linuxthreads/libc-2.3.6.so)
==10859== by 0x1B91FF10: pthread_initialize (in /lib/obsolete/linuxthreads/libpthread-0.10.so)
==10859== by 0x1B925CA1: (within /lib/obsolete/linuxthreads/libpthread-0.10.so)
==10859== by 0x1B91BAE9: (within /lib/obsolete/linuxthreads/libpthread-0.10.so)
==10859== by 0x1B8F1D5A: call_init (in /lib/ld-2.3.6.so)
==10859== by 0x1B8F1E7C: _dl_init (in /lib/ld-2.3.6.so)
==10859== by 0x1B8E47CE: (within /lib/ld-2.3.6.so)
==10859==
==10859== Invalid read of size 1
==10859== at 0x80533C5: (within /data/soldatserver249/soldatserver)
==10859== by 0x1B9812AE: __libc_start_main (in /lib/obsolete/linuxthreads/libc-2.3.6.so)
==10859== by 0x8053743: (within /data/soldatserver249/soldatserver)
==10859== Address 0x52BFEA14 is just below %esp. Possibly a bug in GCC/G++
==10859== v 2.96 or 3.0.X. To suppress, use: --workaround-gcc296-bugs=yes
==10859== TRANSLATE: 0x1B9D24FD redirected to 0x1B909AE6

[...] and many more!