DDraceNetwork

@Learath2 the curl bug also happens with self-built curl

heinrich5991

@Learath2 the curl bug also happens with self-built curl

Well, my next step would be confirming curl 8.4.0 selfbuilt works. Then I'd just bisect between 8.4.0 to 8.5.0. But that's just how I like to do it. I'm sure you don't need me telling you how to debug

Well

The new discord mobile client is so buggy :/

12:45

It keeps double sending my messages

Lol

14:01

Integrated spam bot

14:01

Its a feature

14:02

Since last update i have often segmentation fault, right after joining a server. I'm using version 17.4-1, arch linux btw

Aniak

Since last update i have often segmentation fault, right after joining a server. I'm using version 17.4-1, arch linux btw

downgrade libcurl

okay thx

Aniak

Since last update i have often segmentation fault, right after joining a server. I'm using version 17.4-1, arch linux btw

thanks for the report, it's being tracked here: https://github.com/ddnet/ddnet/issues/7636

Curl 8.5.0 causes segfault · Issue #7636 · ddnet/ddnet

Updating to curl 8.5.0 leads to random segfaults in DDNet only (tw 0.7 and all other software that I use have no problems that I know of) Downgrading to curl 8.4.0 fixes it These crashes are segfau...

yeah thats correct

thread 7 "DDNet" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe1c1f6c0 (LWP 8234)]

thread-changed

frame-begin 0 0x7ffff4833f3c
0x00007ffff4833f3c in ?? () from /usr/lib/libcurl.so.4

stopped

(edited)

16:35

But it does not happen, when I wait some time, and then join a server...Some problem with loading skins or sth, as suggested

probably known already but the elasticity tunings are quite buggy, often when falling, even with minimal momentum, there is no bounce

17:37

u need multiple layers

2

18:16

or it can be treated like a tele or freeze tile perhaps and be applied if a tee passes thru it on next tick

18:16

which would be the better solution

Learath2

Well, my next step would be confirming curl 8.4.0 selfbuilt works. Then I'd just bisect between 8.4.0 to 8.5.0. But that's just how I like to do it. I'm sure you don't need me telling you how to debug

thanks for tellign me to bisect it

22:16

I wasn't actually thinking of doing it before you suggested it (edited)

22:16

found a commit though: https://github.com/ddnet/ddnet/issues/7636#issuecomment-1854783651

Learath2

Well, my next step would be confirming curl 8.4.0 selfbuilt works. Then I'd just bisect between 8.4.0 to 8.5.0. But that's just how I like to do it. I'm sure you don't need me telling you how to debug

I opened an upstream bug report, let's hope daniel doesn't haxx off my head: https://github.com/curl/curl/issues/12513

Null pointer crash in destroy_async_data in curl 8.5.0, caused by...

I did this I updated libcurl and DDNet stopped working: ddnet/ddnet#7636. I get the following stacktrace with curl 8.5.0 #0 0x00007ffff4a60f3c in destroy_async_data (async=0x58) at /usr/src/debug/c...

Use fake account if you fear to get unfriendly responses xd

what happened xd