Hello,

running the dmd testsuite for the package build on NixOS fails with some gdb tests.
It looks like it is a problem with gdb used in the system. The breakpoint setting doesn't seem to work.
I thought that maybe somebody has some experience with this and knows what's going on.

Here is the failing output of one of the testcases:

 ... runnable/gdb14225.d            -g -fPIC ()
Test runnable/gdb14225.d failed.  The logged output:
/build/dmd/generated/linux/release/64/dmd -conf= -m64 -Irunnable -g -fPIC  -odtest_results/runnable -oftest_results/runnable/gdb14225_0  runnable/gdb14225.d
gdb test_results/runnable/gdb14225_0 --batch -x test_results/runnable/gdb14225_0.gdb
Breakpoint 1 at 0x4011b4: file ../../druntime/import/object.d, line 2944.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/nix/store/hp8wcylqr14hrrpqap4wdrwzq092wfln-glibc-2.32-37/lib/libthread_db.so.1".

Breakpoint 1, object.dup!(char).dup(const(char)[]) (a=...) at ../../druntime/import/object.d:2944
2944            return _trustedDup!(const(T), T)(a);
RESULT=test_results/runnable/gdb14225_0.gdb:5: Error in sourced command file:
No symbol "lok" in current context.


==============================
Test runnable/gdb14225.d failed: expected rc == 0, exited with rc == 1

On Saturday, 6 March 2021 at 12:39:08 UTC, Thomas Mader wrote:
> Hello,
>
> running the dmd testsuite for the package build on NixOS fails with some gdb tests.
> It looks like it is a problem with gdb used in the system. The breakpoint setting doesn't seem to work.
> I thought that maybe somebody has some experience with this and knows what's going on.

Wow, pretty much everything D-related updated. Thanks! For anyone interested, his PR is here: https://github.com/NixOS/nixpkgs/pull/115265

Whatever happened, it is after version 2.084.0. I didn't have to disable those gdb tests when I tried to update DMD to that version (it's Tilix that failed, not DMD itself). PR: https://github.com/NixOS/nixpkgs/pull/99392. Sorry, that's everything I know :(.