Segmentation faults?

[divVerent]

[18:34:52] <ATI> uh, this RC keeps quittin with segmentation fault

Whoever that was - can you PLEASE provide more information?

Like:

- running the game in a debugger
- getting a core dump

The latter is quite simple: run "ulimit -c unlimited" from a shell and then start the game from that shell. When it crashes, it writes a file with a name like core.3891. You can then open that in gdb:

gdb nexuiz-glx-linux-x86_64 core.3891

and type "bt" to get a backtrace. You can post that here then.

[Zico]

I can finally confirm this bug.

Unfortunately I cannot provide a BT atm.
I'm on vacation and we try to make a little LAN here. The game runs very smoot on three PCs:
- Laptop with SuSE Linux 10.1 (A64 3400+, 512MB RAM, GF5700GO)
- Laptop with WinXP (1,7 Mobile, ATI X700 Mobile, 1024MB)
- PC with SuSE 10.1 (AMD XP3000+, 1024MB, GF6800LE)

Laptops can play very good together. If the PC comes to join the party it crashes after a short while.
This happens if PC is server or client. Sometimes it crashes while playing or even if a Client tries to access the server list (while PC is a server). Only PC crashes with Sig11.

Additionally we expire the following messages on the PC:
LHNET_Read: sendto returned error: Network is unreachable
... if Network activities begin between PC and one of the Laptops. Mostly it crashes shortly after this message(s).

Repeats several times.
As said unfortunately I cannot provide a BT at the moment because I would need to compile the game from source and no one here wants this now
Since I hope this may help a bit. I try to do a BT asap.

All computers run Nexuiz 2.1 stable.

The PC can also play fine in Instant Action and on a created server without other Clients connnected. The fun only begins if others join (or PC joins)

[divVerent]

Repeats several times.
As said unfortunately I cannot provide a BT at the moment because I would need to compile the game from source and no one here wants this now
Since I hope this may help a bit. I try to do a BT asap.

You don't need to compile from source. A backtrace with the memory addresses alone already helps, because when I ran the compile job, I saved the binaries with debug info in http://hector.rbi.informatik.uni-frankf ... 5_v2.1.zip

These binaries are, apart from the debug info, identical to the released ones, so a backtrace just with memory addresses can be "decoded" using these binaries and addr2line. You can also try using these binaries and then get a more readable backtrace using gdb.

[Zico]

I need to take everything back:

Later on that LAN we had the same bug in several other games as well. Now we know it was an *overheating* problem of the graphics card... The "Network is unreachable" bug still exists, but as well in other games. Workaround by entering direct IP works good here...

[esteel]

Sounds like a problem with your dns server or the settings in windows for that dns server..

[Zico]

DNS?
A windows client always recognizes a public server on LAN (not dedicated).
But the Linux Clients never do. Curious for me.
But it's also a bit chaos on our LANs...
Doesn't matter now. I'm lucky this is not a Nexuiz bug

[divVerent]

Oh, I think I know what's going on there.

On the Linux box as root, type "iptables-save". You will probably find some rules. Try finding out why you don't receive broadcasts. But, remember: unless you know what you are doing, do not disable the firewall altogether. If your Nexuiz client has a cl_port of 4711 (you can set that cvar to force it), you can try executing a rule that allows any incoming traffic to that port:

Code: Select all

iptables -I INPUT 1 -p udp --dport 4711 -j ACCEPT

If that doesn't help, look at the output of "ifconfig" and check if all computers use the same netmask. The Windows equivalent of that command is about "ipconfig /all".

[Zico]

There are no iptables rules saved on the linux boxes. SuSE Firefall's also disabled.
As the "network-technician" (my job) in the house I'm always forced to do all the network stuff by myself.
Subnet Mask is okay. We used a default Class-C net 192.168.0.X/24. While testing with the segfaults we jumped over to a Class-A net 10.0.0.X/8.
A bit fishy...
Probably this is another SuSE-mumbo-jumbo. When vacation is over I need to sit down at home and try this out with my head really free again.