Agora receives SIGABRT

[kchulj]

The result is from gdb.

Thread 1 "agora" received signal SIGABRT, Aborted.
0x00007f4eaa4599ff in setjmp ()
   from /lib/ld-musl-x86_64.so.1
(gdb) bt
#0  0x00007f4eaa4599ff in setjmp ()
   from /lib/ld-musl-x86_64.so.1
#1  0x00007f4eaa459b5a in raise ()
   from /lib/ld-musl-x86_64.so.1
#2  0x000055cf95403c2b in _D3std5range10primitives__T5doPutTSQBh5stdio4File17LockingTextWriterTaZQBsFNfKQBsKaZv (r=...,
    e=<error reading variable: Cannot access memory at address 0xfffffffffffffff8>)
    at /usr/include/d/std/range/primitives.d:276

Blocks #1367 (and/or #1362)

[Geod24]

Do you have a reliable way to reproduce this ?

[kchulj]

Do you have a reliable way to reproduce this ?

I'm still testing, but it happens quite randomly.

[Geod24]

I'm saying this because:

1. This is a very generic error and a million things could cause it;
2. It might be related to a bug I noticed on Musl w.r.t. debug infos and I'm going to work on this weekend;

[kchulj]

Update: Yes, this error is reproducible. So far, it has triggered every time I ran the program.

GDB 9.2 and GDB 10.1 show the same error.

[AndrejMitrovic]

I think this was just a symptom of #1367.

@kchulj can you still reproduce the issue?

[kchulj]

I think this was just a symptom of #1367.

@kchulj can you still reproduce the issue?

Will test with the update.

[kchulj]

Tested with latest version of agora on the servers and the assert no longer triggers.
This issue can be closed now.

[Geod24]

The bug is actually in the backtrace code, upstream.

[AndrejMitrovic]

Is there a ticket upstream we can link to? Let's add it to #561.

[kchulj]

Is there a ticket upstream we can link to? Let's add it to #561.

I'll add #21442 , but it's not exactly related to this issue.
We need a new ticket for this.

[Geod24]

No ticket upstream yet, because it's not an upstream bug. It's merely an enhancement, and unrelated to 21442 (although it might have made the issue more obvious).

[AndrejMitrovic]

I'll add #21442

I already added that one.