Scud launch crashes linux server?!?

[benu 1]

I just got a report from one of my players that launching a scud crashes my server. I could recreate this bug, using a mission where you start as a scud driver. This happens on a linux server with 1.92 and 1.91 too. I just set up another linux server, just a fresh windows install copied over to linux, tolower and flashpoint.cfg and server.cfg. Same problem. I made an strace (-eopen), last lines are:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

open("mpmissions/scud_test.noe.pbo", O_RDONLY) = 42

open("mpmissions/scud_test.noe.pbo", O_RDONLY) = 42

open("mpmissions/scud_test.noe.pbo", O_RDONLY) = 42

open("mpmissions/cur_mp.noe/description.ext", O_RDONLY) = -1 ENOENT (No such file or directory)

open("mpmissions/scud_test.noe.pbo", O_RDONLY) = 43

open("mpmissions/scud_test.noe.pbo", O_RDONLY) = 43

open("mpmissions/scud_test.noe.pbo", O_RDONLY) = 42

open("/proc/22453/statm", O_RDONLY) = 42

open("o/hous/kasna01_dno.06.pac", O_RDONLY) = -1 ENOENT (No such file or directory)

open("o/hous/kasna01_hladina.06.paa", O_RDONLY) = -1 ENOENT (No such file or directory)

open("sound/environmental/wave_break.wss", O_RDONLY) = -1 ENOENT (No such file or directory)

open("res/dta/anim.pbo", O_RDONLY) = 42

open("data/zasleh_front.04.paa", O_RDONLY) = -1 ENOENT (No such file or directory)

open("data/zasleh_side.04.paa", O_RDONLY) = -1 ENOENT (No such file or directory)

open("data/zasleh3_front.04.paa", O_RDONLY) = -1 ENOENT (No such file or directory)

open("data/zasleh3_side.04.paa", O_RDONLY) = -1 ENOENT (No such file or directory)

open("tmp/squads/-=ldd=-/logo_ds.paa", O_RDONLY) = 43

open("tmp/squads/-=ldd=-/logo_ds.paa", O_RDONLY) = 43

open("tmp/players/benu/face.paa", O_RDONLY) = -1 ENOENT (No such file or directory)

open("tmp/players/benu/face.jpg", O_RDONLY) = -1 ENOENT (No such file or directory)

open("mpmissions/scud_test.noe.pbo", O_RDONLY) = 44

open("mpmissions/__cur_mp.noe/init.sqs", O_RDONLY) = -1 ENOENT (No such file or directory)

--- SIGRTMIN (Unknown signal 32) @ 0 (0) ---

open("/proc/22453/statm", O_RDONLY) = 45

open("/proc/22453/statm", O_RDONLY) = 45

--- SIGRTMIN (Unknown signal 32) @ 0 (0) ---

--- SIGRTMIN (Unknown signal 32) @ 0 (0) ---

--- SIGRTMIN (Unknown signal 32) @ 0 (0) ---

--- SIGRTMIN (Unknown signal 32) @ 0 (0) ---

--- SIGSEGV (Segmentation fault) @ 0 (0) ---

+++ killed by SIGSEGV +++

Can anyone with a linux server reproduce this or is it a mistake on my part?

BTW: is #init working on linux servers yet? Last time i checked it wasn't...

[kegetys 2]

Crashed my test server too

[GODSMACK 0]

it happens at radishville, which is linux. we always joke that the scuds are targeting the server

[benu 1]

So it seems there are some bugs left in the linux server, and i think a bug which crashes the server could be considered serious

[HitmanFF 6]

Crashing of a SCUD launch on a linux server has been posted before on the 1.91 feedback thread

I remember, since I posted on the subject myself

[pepca 0]

This bug has been fixed - next distribution 1.93 will be available soon.

We are working on the "No message received ..." issue, so be patient.

[benu 1]

That's great news. Any chance that #init will be implemented for linux servers too? Cause right now you have to restart the server for every little change

[Pennywise 0]

I have been barking about this a long time.  I sent them several emails and examples.  Its nice to see they finally fixed the bug.

Scud Bug

[Pennywise 0]

I have also noticed grouping and joining work differently in linux as well.  Sometimes men want even spawn using the createunit command where they work in win32.

[benu 1]

Will this bug(?) be fixed too?