lix/tests/unit/libstore
jade 519957bd59 unnamed threads: Obliterate
Ever read gdb output and you just kinda get a headache because you have
to infer what a thread is by reading the stack trace? It's not hard, but
we could also just never have to do that again, which is also not hard.

Sample:

(gdb) info thr
  Id   Target Id                    Frame
* 1    LWP 3719283 "nix-daemon"     0x00007e558587da0f in accept ()
   from target:/nix/store/c10zhkbp6jmyh0xc5kd123ga8yy2p4hk-glibc-2.39-52/lib/libc.so.6
  2    LWP 3719284 "signal handler" 0x00007e55857b2bea in sigtimedwait ()
   from target:/nix/store/c10zhkbp6jmyh0xc5kd123ga8yy2p4hk-glibc-2.39-52/lib/libc.so.6

The API design for this is forced by the macOS pthread_setname_np only
being able to change the current thread's name, but if we just conform
everything to that, it works everywhere.

Change-Id: I2b1d6ed41e3c94170cb0b4e73ad66f239ebd9c88
2024-11-18 18:53:40 -08:00
..
data Delete old ValidPathInfo test, fix UnkeyedValidPathInfo 2024-06-16 19:13:51 -07:00
common-protocol.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00
derivation.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00
derived-path.cc derived-path: refuse built derived path with a non-derivation base 2024-05-17 02:16:15 +02:00
downstream-placeholder.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00
filetransfer.cc unnamed threads: Obliterate 2024-11-18 18:53:40 -08:00
machines.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00
nar-info-disk-cache.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00
outputs-spec.cc Fix various clang-tidy lints 2024-03-29 20:26:38 -07:00
path.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00
protocol.hh Include rearrangement: rest 2024-11-18 12:31:19 -08:00
references.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00
serve-protocol.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00
worker-protocol.cc Include rearrangement: rest 2024-11-18 12:31:19 -08:00