Teeworlds - bridge

Teeworlds

IRC / bridge

One-way IRC channel bridge. If you want to be able to send messages to IRC, contact @Dune or @heinrich5991. https://www.teeworlds.com/?page=docs&wiki=rules/irc_rules

Between 2021-01-22 00:00:00Z and 2021-01-23 00:00:00Z

Hello ChillerDragon, did you server have a blip very recently?

14:52

Teeworlds crashed whilst I was on your server, you see. Others playing also had Teeworlds crash on them

whats a blip?

15:12

Did you have an actual client crash? Or just laggs on the server?

thanos reference i guess

Indeed, an actual client crash

15:12

I think everyone else on the server had it too

wtf

15:13

what makes you think that others crashed too?

They told me in the chat

and what client are you using?

Err... let me check

lol vanilla server being vanilla client crasher

15:13

something makes me doubt that

sus

OK I asked the package manager; it's teeworlds-0.7.5-1.fc31

15:14

(fc31 being a Fedora version)

oof

ooh a bug report by abrt

15:15

SIGSEGV

yikes

15:16

nice time to write some tw exploits

hope not :/

do you have a backtrace or a coredump?

I'm looking... I hardly know abrt

15:17

Do you know how to use abrt?

hm no

15:17

when did it happen maybe i see somethign in the logs

14:40:24

15:23

OK I can give you the backtrace :)

15:23

https://x0.at/khk.txt

15:25

Hmm I don't like these two lines:

15:25

Likely crash reason: Jump to an invalid address

15:25

Exploitable rating (0-9 scale): 6

yikers

15:43

maybe open a issue on github if you have this nice trace

OK... I don't have a Github account, but maybe...

15:45

Did you see anything weird on your end?

i can confrim that at 14:40 multiple tees left the server

hmm so clearly a client-side bug

15:50

but not all tees?

no not all

15:52

this looks bad

hmm can you, as a server admin, see which versions the tees where in?

15:52

like maybe it's been fixed upstream and I'm just out of date

do you have a demo of it?

15:52

maybe it has some hints

15:53

i think versions are not logged

15:53

well i mean i see that versions are not logged xd

15:53

I guess ill open a issue with ur backtrace then

15:55

can you maybe send your client binary

15:55

maybe in combination with the offset in the backtrace that can be useful

15:55

im not a debugging guru

15:55

@Learath2 @heinrich5991 alert client segfault

send the binary?

15:56

Like all of it?

what an odd backtrace, can't figure out what the offsets are without the binary as it seems to be a release build

OK - it might be Red Hat messing with it

15:57

you know how Fedora is with binaries :)

lol rly?

Well, they removed emacs tetris because of trademark concerns

15:58

in fact they removed it twice, but left the command in

so where can we get the binary now?

Erm, I can't even find it

16:01

sorry :D

yikes

no no it's just Firejail weirdness

16:02

/usr/local/bin/teeworlds -> /usr/bin/firejail

dfq

got it

16:03

./teeworlds: ELF 64-bit LSB pie executable

16:03

here's the sum to start with: sha256sum

16:03

a45afb1c1b52f19df025b7e55041b01313d28756901b46ee752b39de15be358b

yay

https://x0.at/cEz.bin

16:06

is the actual binary

do you have autorecord demos on?

nope :(

sad

well I can't reproduce it

seabass: https://github.com/teeworlds/teeworlds/issues/2848

Client crash 0.7.5 CGameClient::OnRender() · Issue #2848 · teeworld...

seabass reported a client crash on a vanilla server (server commit: 42b2bbd server map: ctf5) checking the logs I can confirm about 8 players lost connection to the server and 3 survived. seabass w...

ChillerDragon, thanks :)

16:18

I'll watch the issue and try and learn some GDB maybe as well :)

try llldb

17:18

lldb

Exported 85 message(s)