Single stepping until exit from function read, which has no line number information. [GDB] Can't debug

I’m debugging with
gcc v10.1.0
gdb v9.2

JUCE v6.0.1 but I had it before with JUCE 5 as well. Before it worked fine, might be a breaking update in gcc or gdb.

I tried compiling with -g and -ggdb to no avail. Debugging with plain cpp files works flawlessly

[Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". JUCE v6.0.1
[New Thread 0x7ffff3301700 (LWP 10631) [New Thread 0x7fff3183700 (LWP 10632)] Thread 3 "GeoHead received signal SIG32, Real-time event 32. [Switching to Thread 0x7ffff3183700 (LWP 10632) 0x00007ffff736387c in read () from /usr/lib/libpthread.so.0 Single stepping until exit from function read, which has no line number information. Single stepping until exit from function sigcancel_handler, which has no line number information.
Single stepping until exit from function start_thread, which has no line number information. [Thread 0x7ffff3183700 (LWP 10632) exited] Thread 2 "GeoHead" received SIGTRAp, Trace/breakpoint trap. [Switching to thread 7xfff3183700 (LWP 10631)]0x00007ffff6 e89108 in _longjmp_cancel () from /usr/lib/libc.so6 Single stepping until exit from function __longjmp_cancel, which has no line number information.

Nobody? I think this is a JUCE bug

I’ve just compiled the DemoRunner on Ubuntu 18.04 with GCC 10.1.0 and run it under GDB 9.2 and am able to set breakpoints and step through the code without issue. It looks like it could be an issue with libpthread - which Linux distribution are you using?

Manjaro openbox

Nobody knows what this is? I still have this problem