bug#66610: potrace, po4a; guix bug, complete console output

bug#66610: potrace, po4a; guix bug, complete console output

[Olav Smorholm]

building /gnu/store/w63ra4pwqvk9ii5zf4piksf4kyddvz3p-potrace-1.16.drv...
\Backtrace:
In ice-9/eval.scm:
    155:9 19 (_ _)
    159:9 18 (_ #(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#<directory (guile-u?> ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
In ice-9/boot-9.scm:
    152:2 17 (with-fluid* _ _ _)
    152:2 16 (with-fluid* _ _ _)
In ./guix/store.scm:
  2168:24 15 (run-with-store #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bf66e6730 at ./guix/self.scm:13?> ?)
   1996:8 14 (_ #<store-connection 256.99 7f3c0bbc10a0>)
In ./guix/gexp.scm:
   299:22 13 (_ #<store-connection 256.99 7f3c0bbc10a0>)
   1180:2 12 (_ #<store-connection 256.99 7f3c0bbc10a0>)
   1046:2 11 (_ #<store-connection 256.99 7f3c0bbc10a0>)
    892:4 10 (_ #<store-connection 256.99 7f3c0bbc10a0>)
In ./guix/store.scm:
  2053:12  9 (_ #<store-connection 256.99 7f3c0bbc10a0>)
  1405:13  8 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3becda5560 at ./guix/stor?> ?)
  1405:13  7 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bdcb89240 at ./guix/stor?> ?)
  1405:13  6 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bfb1fcfa0 at ./guix/stor?> ?)
  1405:13  5 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bdeace6a0 at ./guix/stor?> ?)
  1405:13  4 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bde19d440 at ./guix/stor?> ?)
  1405:13  3 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bfa7f3940 at ./guix/stor?> ?)
   1401:5  2 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bf49c2b00 at ./guix/stor?> ?)
  1417:15  1 (_ #<store-connection 256.99 7f3c0bbc10a0> ("/gnu/store/y4cbrpv0dxsdjg8w2mb702p77xszp9p8-po4a-0.69.drv") ?)
  1417:15  0 (loop #f)

./guix/store.scm:1417:15: In procedure loop:
ERROR:
  1. &store-protocol-error:
      message: "build of `/gnu/store/y4cbrpv0dxsdjg8w2mb702p77xszp9p8-po4a-0.69.drv' failed"
      status: 100
guix pull: error: You found a bug: the program '/gnu/store/bir38i1c1nwbfkbhgprn3c9bp23q5i1w-compute-guix-derivation'
failed to compute the derivation for Guix (version: "7823c6504082a0cfbd98beb301e041fb8bc4e44e"; system: "x86_64-linux";
host version: "e80022ff3adde3184bed6758f604e3aa12942865"; pull-version: 1).
Please report the COMPLETE output above by email to <bug-guix@gnu.org>.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

This may be relevant dmesg, where all should be from guix bootstrap on
gentoo-musl hardened after garbage collecting, guix pull and update.
I have enabled unsafe(rnd) kernel options security and hardening options.
So the bug may have revealed itself here. A few of these lines are
suspicious, and xsltproc may coincide, and tripped by kernel not safe
for bugs.
xsltproc[29510]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6
Below this is a refresh of guix pull and update.



[16584.148847] ld.lld[15969]: segfault at 8 ip 00007ffff1cba4f4 sp 00007ffd747f77d8 error 4 in libLLVM-15.so[7ffff133f000+3c17000] likely on CPU 10 (core 4, socket 0)
[16584.148867] Code: b6 50 08 80 fa 0d 0f 94 c0 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8b 47 08 80 78 08 0d 0f 94 c0 c3 0f 1f 40 00 48 8b 47 08 <0f> b6 40 08 83 e8 12 83 f8 01 0f 96 c0 c3 66 2e 0f 1f 84 00 00 00
[22073.399589] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
[23083.553485] mes[21949]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 1 (core 1, socket 0)
[23083.553504] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
[44199.655173] traps: conftest[11508] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
[47929.916650] test-recvmsg[1981]: segfault at 0 ip 00007f6d870cc7d5 sp 00007ffcf61165e0 error 4 in libc.so[7f6d8709a000+62000] likely on CPU 12 (core 8, socket 0)
[47929.916668] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
[47944.249962] test-recvmsg[4022]: segfault at 0 ip 00007fe08edc87d5 sp 00007fff60fed1e0 error 4 in libc.so[7fe08ed96000+62000] likely on CPU 8 (core 0, socket 0)
[47944.249980] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
[86977.669680] NET: Registered PF_ALG protocol family
[87794.000878] xsltproc[29510]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 8 (core 0, socket 0)
[87794.000896] Code: 00 48 89 c2 4c 8d 4a 10 48 8b 42 10 4c 89 ce 48 c1 ee 0c 49 89 f0 49 31 c0 48 39 c6 74 be eb ac 0f 1f 40 00 48 89 d8 48 89 d9 <44> 89 64 24 30 48 c1 e8 06 48 c1 e9 09 c7 44 24 78 6e 00 00 00 48
[88930.006298] cmsysTestProces[556]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 1 (core 1, socket 0)
[88930.006316] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
[88930.013815] cmsysTestProces[563]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 9 (core 1, socket 0)
[88930.013830] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
[88963.001638] Crash[1983]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
[88963.001656] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
[89271.158500] cmsysTestProces[18868]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 1 (core 1, socket 0)
[89271.158518] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
[89271.162994] cmsysTestProces[18881]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
[89271.163010] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
[89298.998091] Crash[18308]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 3 (core 5, socket 0)
[89298.998108] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

Tried to reproduce, but with no substitutes and no grafts.
Wed Oct 18 18:48:34 2023] mes[19410]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 4 (core 8, socket 0)
[Wed Oct 18 18:48:34 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00

Which should be the first, and perhaps only one before conf and tests.
Reported as guix binary requested with caveats that while GNU, i tend to opt
for UNIX crashy. and could be hard to chase with coincidence mixed in;
hard to chase.

On Wed, Oct 18, 2023 at 05:34:50PM +0200, Olav Smorholm wrote:
> This may be relevant dmesg, where all should be from guix bootstrap on
> gentoo-musl hardened after garbage collecting, guix pull and update.
> I have enabled unsafe(rnd) kernel options security and hardening options.
> So the bug may have revealed itself here. A few of these lines are
> suspicious, and xsltproc may coincide, and tripped by kernel not safe
> for bugs.
> xsltproc[29510]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6
> Below this is a refresh of guix pull and update.
> 
> 
> 
> [16584.148847] ld.lld[15969]: segfault at 8 ip 00007ffff1cba4f4 sp 00007ffd747f77d8 error 4 in libLLVM-15.so[7ffff133f000+3c17000] likely on CPU 10 (core 4, socket 0)
> [16584.148867] Code: b6 50 08 80 fa 0d 0f 94 c0 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8b 47 08 80 78 08 0d 0f 94 c0 c3 0f 1f 40 00 48 8b 47 08 <0f> b6 40 08 83 e8 12 83 f8 01 0f 96 c0 c3 66 2e 0f 1f 84 00 00 00
> [22073.399589] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
> [23083.553485] mes[21949]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 1 (core 1, socket 0)
> [23083.553504] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
> [44199.655173] traps: conftest[11508] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
> [47929.916650] test-recvmsg[1981]: segfault at 0 ip 00007f6d870cc7d5 sp 00007ffcf61165e0 error 4 in libc.so[7f6d8709a000+62000] likely on CPU 12 (core 8, socket 0)
> [47929.916668] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [47944.249962] test-recvmsg[4022]: segfault at 0 ip 00007fe08edc87d5 sp 00007fff60fed1e0 error 4 in libc.so[7fe08ed96000+62000] likely on CPU 8 (core 0, socket 0)
> [47944.249980] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [86977.669680] NET: Registered PF_ALG protocol family
> [87794.000878] xsltproc[29510]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 8 (core 0, socket 0)
> [87794.000896] Code: 00 48 89 c2 4c 8d 4a 10 48 8b 42 10 4c 89 ce 48 c1 ee 0c 49 89 f0 49 31 c0 48 39 c6 74 be eb ac 0f 1f 40 00 48 89 d8 48 89 d9 <44> 89 64 24 30 48 c1 e8 06 48 c1 e9 09 c7 44 24 78 6e 00 00 00 48
> [88930.006298] cmsysTestProces[556]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 1 (core 1, socket 0)
> [88930.006316] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [88930.013815] cmsysTestProces[563]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 9 (core 1, socket 0)
> [88930.013830] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [88963.001638] Crash[1983]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
> [88963.001656] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> [89271.158500] cmsysTestProces[18868]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 1 (core 1, socket 0)
> [89271.158518] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [89271.162994] cmsysTestProces[18881]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
> [89271.163010] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [89298.998091] Crash[18308]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 3 (core 5, socket 0)
> [89298.998108] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> 

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Wed, Oct 18, 2023 at 11:21:06PM +0200, Olav Smorholm wrote:
> Tried to reproduce, but with no substitutes and no grafts.
> Wed Oct 18 18:48:34 2023] mes[19410]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 4 (core 8, socket 0)
> [Wed Oct 18 18:48:34 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
> 
> Which should be the first, and perhaps only one before conf and tests.
> Reported as guix binary requested with caveats that while GNU, i tend to opt
> for UNIX crashy. and could be hard to chase with coincidence mixed in;
> hard to chase.

took much longer with --no-grafts and --no-substitutes, but this also
showed up again, but not the seed.

[Thu Oct 19 12:18:54 2023] xsltproc[5943]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000]

still fairly sure its from guix building.

[Tue Oct 17 21:33:19 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Thu, Oct 19, 2023 at 03:05:01PM +0200, Olav Smorholm wrote:
> On Wed, Oct 18, 2023 at 11:21:06PM +0200, Olav Smorholm wrote:
> > Tried to reproduce, but with no substitutes and no grafts.
> > Wed Oct 18 18:48:34 2023] mes[19410]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 4 (core 8, socket 0)
> > [Wed Oct 18 18:48:34 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
> > 
> > Which should be the first, and perhaps only one before conf and tests.
> > Reported as guix binary requested with caveats that while GNU, i tend to opt
> > for UNIX crashy. and could be hard to chase with coincidence mixed in;
> > hard to chase.
> 
> took much longer with --no-grafts and --no-substitutes, but this also
> showed up again, but not the seed.
> 
> [Thu Oct 19 12:18:54 2023] xsltproc[5943]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000]
> 
> still fairly sure its from guix building.
> 
> [Tue Oct 17 21:33:19 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack

Reboot, and by not checking, into rebuild kernel without the pattern
init unsafe hardening options. For an hour and half, the only thing I
see is this:
Thu Oct 19 16:57:16 2023] process 'store/5srp88m0d10qxnb49c3sa2a186kjy6xz-tcc-boot-0.9.27/bin/tcc' started with executable stack

Instead of the seed, and no mes segfaults, and will do this again.
It's a bit of a stretch to say I had a rodent i here segfaulted my way
out of, but I dont live in any of the relevant information structures
between compiler assembly, running code and debuggers. Nor familiarity
enough to say why tcc is said to be started with executable stack
instead of the seed as above. I am just fairly certain that something
isn't house clean in what is inherently complicated and bootstrap that
touches many fundamental things.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Thu, Oct 19, 2023 at 06:29:07PM +0200, Olav Smorholm wrote:
> On Thu, Oct 19, 2023 at 03:05:01PM +0200, Olav Smorholm wrote:
> > On Wed, Oct 18, 2023 at 11:21:06PM +0200, Olav Smorholm wrote:
> > > Tried to reproduce, but with no substitutes and no grafts.
> > > Wed Oct 18 18:48:34 2023] mes[19410]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 4 (core 8, socket 0)
> > > [Wed Oct 18 18:48:34 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
> > > 
> > > Which should be the first, and perhaps only one before conf and tests.
> > > Reported as guix binary requested with caveats that while GNU, i tend to opt
> > > for UNIX crashy. and could be hard to chase with coincidence mixed in;
> > > hard to chase.
> > 
> > took much longer with --no-grafts and --no-substitutes, but this also
> > showed up again, but not the seed.
> > 
> > [Thu Oct 19 12:18:54 2023] xsltproc[5943]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000]
> > 
> > still fairly sure its from guix building.
> > 
> > [Tue Oct 17 21:33:19 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
> 
> Reboot, and by not checking, into rebuild kernel without the pattern
> init unsafe hardening options. For an hour and half, the only thing I
> see is this:
> Thu Oct 19 16:57:16 2023] process 'store/5srp88m0d10qxnb49c3sa2a186kjy6xz-tcc-boot-0.9.27/bin/tcc' started with executable stack
> 
> Instead of the seed, and no mes segfaults, and will do this again.
> It's a bit of a stretch to say I had a rodent i here segfaulted my way
> out of, but I dont live in any of the relevant information structures
> between compiler assembly, running code and debuggers. Nor familiarity
> enough to say why tcc is said to be started with executable stack
> instead of the seed as above. I am just fairly certain that something
> isn't house clean in what is inherently complicated and bootstrap that
> touches many fundamental things.
> 

Another reboot with more hardening things:
process 'store/9cfq2h8sa5f6cgrhdgadlxwkf00vmgf5-gcc-mesboot1-4.6.4/bin/gcc' started with executable stack

and absolutely no segfaults.
either bugs got more clever, or this isn't house clean.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Fri, Oct 20, 2023 at 12:36:48AM +0200, Olav Smorholm wrote:
> Another reboot with more hardening things:
> process 'store/9cfq2h8sa5f6cgrhdgadlxwkf00vmgf5-gcc-mesboot1-4.6.4/bin/gcc' started with executable stack
> 
> and absolutely no segfaults.
> either bugs got more clever, or this isn't house clean.
> 

Another --no-substitutes --no-grafts guix pull after garbage collection.

Not seeing any crashes or the same bugs, but whatever that xsltproc is, whether docbooks
perl script ot not. Whatever it is doing, or what it is, that trigger
PF_ALG; it doesnt look nice.

[Fri Oct 20 22:34:22 2023] elogind-daemon[2265]: New session 1...
[Fri Oct 20 22:34:31 2023] wezterm-gui[3001]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
[Fri Oct 20 22:37:54 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
[Fri Oct 20 22:51:30 2023] mes[13170]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 7 (core 13, socket 0)
[Fri Oct 20 22:51:30 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
[Sat Oct 21 04:07:49 2023] traps: conftest[7164] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
[Sat Oct 21 15:22:01 2023] NET: Registered PF_ALG protocol family
[Sat Oct 21 15:33:47 2023] xsltproc[20127]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 0 (core 0, socket 0)
[Sat Oct 21 15:33:47 2023] Code: 00 48 89 c2 4c 8d 4a 10 48 8b 42 10 4c 89 ce 48 c1 ee 0c 49 89 f0 49 31 c0 48 39 c6 74 be eb ac 0f 1f 40 00 48 89 d8 48 89 d9 <44> 89 64 24 30 48 c1 e8 06 48 c1 e9 09 c7 44 24 78 6e 00 00 00 48
[Sat Oct 21 15:42:15 2023] cmsysTestProces[17226]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 10 (core 4, socket 0)
[Sat Oct 21 15:42:15 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
[Sat Oct 21 15:42:15 2023] cmsysTestProces[17242]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
[Sat Oct 21 15:42:15 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
[Sat Oct 21 15:42:55 2023] Crash[30912]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
[Sat Oct 21 15:42:55 2023] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
[Sat Oct 21 15:48:06 2023] cmsysTestProces[7756]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
[Sat Oct 21 15:48:06 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
[Sat Oct 21 15:48:06 2023] cmsysTestProces[7766]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
[Sat Oct 21 15:48:06 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
[Sat Oct 21 15:48:36 2023] Crash[12401]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 6 (core 12, socket 0)
[Sat Oct 21 15:48:36 2023] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Sat, Oct 21, 2023 at 04:57:52PM +0200, Olav Smorholm wrote:
> Another --no-substitutes --no-grafts guix pull after garbage collection.
> 
> Not seeing any crashes or the same bugs, but whatever that xsltproc is, whether docbooks
> perl script ot not. Whatever it is doing, or what it is, that trigger
> PF_ALG; it doesnt look nice.
> 
> [Fri Oct 20 22:34:22 2023] elogind-daemon[2265]: New session 1...
> [Fri Oct 20 22:34:31 2023] wezterm-gui[3001]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
> [Fri Oct 20 22:37:54 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
> [Fri Oct 20 22:51:30 2023] mes[13170]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 7 (core 13, socket 0)
> [Fri Oct 20 22:51:30 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
> [Sat Oct 21 04:07:49 2023] traps: conftest[7164] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
> [Sat Oct 21 15:22:01 2023] NET: Registered PF_ALG protocol family
> [Sat Oct 21 15:33:47 2023] xsltproc[20127]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 0 (core 0, socket 0)
> [Sat Oct 21 15:33:47 2023] Code: 00 48 89 c2 4c 8d 4a 10 48 8b 42 10 4c 89 ce 48 c1 ee 0c 49 89 f0 49 31 c0 48 39 c6 74 be eb ac 0f 1f 40 00 48 89 d8 48 89 d9 <44> 89 64 24 30 48 c1 e8 06 48 c1 e9 09 c7 44 24 78 6e 00 00 00 48
> [Sat Oct 21 15:42:15 2023] cmsysTestProces[17226]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 10 (core 4, socket 0)
> [Sat Oct 21 15:42:15 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [Sat Oct 21 15:42:15 2023] cmsysTestProces[17242]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
> [Sat Oct 21 15:42:15 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [Sat Oct 21 15:42:55 2023] Crash[30912]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
> [Sat Oct 21 15:42:55 2023] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> [Sat Oct 21 15:48:06 2023] cmsysTestProces[7756]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
> [Sat Oct 21 15:48:06 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [Sat Oct 21 15:48:06 2023] cmsysTestProces[7766]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
> [Sat Oct 21 15:48:06 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [Sat Oct 21 15:48:36 2023] Crash[12401]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 6 (core 12, socket 0)
> [Sat Oct 21 15:48:36 2023] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08

Whatever the initial guix bug was or what bitrot and system quirks that
may be involved.

There is inherent room for a moral appeal around K&R(Ken Thompson and
Dennis Ritchie) legendary and classical systems security problems.

That accessibility, where interest is ensured, not really seeing
sufficiently amounts of assembly code and integrated circuits amateurs
in lack of professionals with hobbies.

Admitting to the existance of preferences of psychological nature that
influence social and ideological adherance from necessity between
natural and moral activity understood as practical vs cultural.
For GNU this line and differences is inherently strengthened.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Sat, Oct 21, 2023 at 07:12:13PM +0200, Olav Smorholm wrote:
> On Sat, Oct 21, 2023 at 04:57:52PM +0200, Olav Smorholm wrote:
> > Another --no-substitutes --no-grafts guix pull after garbage collection.
> > 
> > Not seeing any crashes or the same bugs, but whatever that xsltproc is, whether docbooks
> > perl script ot not. Whatever it is doing, or what it is, that trigger
> > PF_ALG; it doesnt look nice.
> > 
> > [Fri Oct 20 22:34:22 2023] elogind-daemon[2265]: New session 1...
> > [Fri Oct 20 22:34:31 2023] wezterm-gui[3001]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
> > [Fri Oct 20 22:37:54 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
> > [Fri Oct 20 22:51:30 2023] mes[13170]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 7 (core 13, socket 0)
> > [Fri Oct 20 22:51:30 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
> > [Sat Oct 21 04:07:49 2023] traps: conftest[7164] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
> > [Sat Oct 21 15:22:01 2023] NET: Registered PF_ALG protocol family
> > [Sat Oct 21 15:33:47 2023] xsltproc[20127]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 0 (core 0, socket 0)
> > [Sat Oct 21 15:33:47 2023] Code: 00 48 89 c2 4c 8d 4a 10 48 8b 42 10 4c 89 ce 48 c1 ee 0c 49 89 f0 49 31 c0 48 39 c6 74 be eb ac 0f 1f 40 00 48 89 d8 48 89 d9 <44> 89 64 24 30 48 c1 e8 06 48 c1 e9 09 c7 44 24 78 6e 00 00 00 48
> > [Sat Oct 21 15:42:15 2023] cmsysTestProces[17226]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 10 (core 4, socket 0)
> > [Sat Oct 21 15:42:15 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> > [Sat Oct 21 15:42:15 2023] cmsysTestProces[17242]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
> > [Sat Oct 21 15:42:15 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> > [Sat Oct 21 15:42:55 2023] Crash[30912]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
> > [Sat Oct 21 15:42:55 2023] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> > [Sat Oct 21 15:48:06 2023] cmsysTestProces[7756]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
> > [Sat Oct 21 15:48:06 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> > [Sat Oct 21 15:48:06 2023] cmsysTestProces[7766]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
> > [Sat Oct 21 15:48:06 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> > [Sat Oct 21 15:48:36 2023] Crash[12401]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 6 (core 12, socket 0)
> > [Sat Oct 21 15:48:36 2023] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> 
> Whatever the initial guix bug was or what bitrot and system quirks that
> may be involved.
> 
> There is inherent room for a moral appeal around K&R(Ken Thompson and
> Dennis Ritchie) legendary and classical systems security problems.
> 
> That accessibility, where interest is ensured, not really seeing
> sufficiently amounts of assembly code and integrated circuits amateurs
> in lack of professionals with hobbies.
> 
> Admitting to the existance of preferences of psychological nature that
> influence social and ideological adherance from necessity between
> natural and moral activity understood as practical vs cultural.
> For GNU this line and differences is inherently strengthened.

If you were a worm, and especially in PF_ALG to play with crypto or
intensive tasks. You would lie and name yourself any of the above test
processes that may not be ncessary at all.

If and only if, you were a Intel Research employee that work on Intel C compiler
you'd be interested, and may require some omissions for time investments
with the best possible outcome being an article about it.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Sat, Oct 21, 2023 at 08:29:50PM +0200, Olav Smorholm wrote:
> On Sat, Oct 21, 2023 at 07:12:13PM +0200, Olav Smorholm wrote:
> > On Sat, Oct 21, 2023 at 04:57:52PM +0200, Olav Smorholm wrote:
> > > Another --no-substitutes --no-grafts guix pull after garbage collection.
> > > 
> > > Not seeing any crashes or the same bugs, but whatever that xsltproc is, whether docbooks
> > > perl script ot not. Whatever it is doing, or what it is, that trigger
> > > PF_ALG; it doesnt look nice.
> > > 
> > > [Fri Oct 20 22:34:22 2023] elogind-daemon[2265]: New session 1...
> > > [Fri Oct 20 22:34:31 2023] wezterm-gui[3001]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
> > > [Fri Oct 20 22:37:54 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
> > > [Fri Oct 20 22:51:30 2023] mes[13170]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 7 (core 13, socket 0)
> > > [Fri Oct 20 22:51:30 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
> > > [Sat Oct 21 04:07:49 2023] traps: conftest[7164] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
> > > [Sat Oct 21 15:22:01 2023] NET: Registered PF_ALG protocol family
> > > [Sat Oct 21 15:33:47 2023] xsltproc[20127]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 0 (core 0, socket 0)
> > > [Sat Oct 21 15:33:47 2023] Code: 00 48 89 c2 4c 8d 4a 10 48 8b 42 10 4c 89 ce 48 c1 ee 0c 49 89 f0 49 31 c0 48 39 c6 74 be eb ac 0f 1f 40 00 48 89 d8 48 89 d9 <44> 89 64 24 30 48 c1 e8 06 48 c1 e9 09 c7 44 24 78 6e 00 00 00 48
> > > [Sat Oct 21 15:42:15 2023] cmsysTestProces[17226]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 10 (core 4, socket 0)
> > > [Sat Oct 21 15:42:15 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> > > [Sat Oct 21 15:42:15 2023] cmsysTestProces[17242]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
> > > [Sat Oct 21 15:42:15 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> > > [Sat Oct 21 15:42:55 2023] Crash[30912]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
> > > [Sat Oct 21 15:42:55 2023] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> > > [Sat Oct 21 15:48:06 2023] cmsysTestProces[7756]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
> > > [Sat Oct 21 15:48:06 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> > > [Sat Oct 21 15:48:06 2023] cmsysTestProces[7766]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
> > > [Sat Oct 21 15:48:06 2023] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> > > [Sat Oct 21 15:48:36 2023] Crash[12401]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 6 (core 12, socket 0)
> > > [Sat Oct 21 15:48:36 2023] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> > 
> > Whatever the initial guix bug was or what bitrot and system quirks that
> > may be involved.
> > 
> > There is inherent room for a moral appeal around K&R(Ken Thompson and
> > Dennis Ritchie) legendary and classical systems security problems.
> > 
> > That accessibility, where interest is ensured, not really seeing
> > sufficiently amounts of assembly code and integrated circuits amateurs
> > in lack of professionals with hobbies.
> > 
> > Admitting to the existance of preferences of psychological nature that
> > influence social and ideological adherance from necessity between
> > natural and moral activity understood as practical vs cultural.
> > For GNU this line and differences is inherently strengthened.
> 
> If you were a worm, and especially in PF_ALG to play with crypto or
> intensive tasks. You would lie and name yourself any of the above test
> processes that may not be ncessary at all.
> 
> If and only if, you were a Intel Research employee that work on Intel C compiler
> you'd be interested, and may require some omissions for time investments
> with the best possible outcome being an article about it.

Changing one configure, or nesting it does require an article.
Because sometimes, it's intact code written by living legends like
Stallmnan, Ritchie or Thompson; don't care if it may segfault.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Sat, Oct 21, 2023 at 08:52:13PM +0200, Olav Smorholm wrote:
>

And call it, or view is it as you may; no trivial task to determine if
the guix binary bug and crash was useful or not.

But in the process, while for other things after; starting to study
dmesg. Bluez and related things that awaken bluetooth kernel subsystems
is less of an aesthetic problem.

I react somewhat on PF_ALG especially, weird segfault that calls itself
xsltproc, and that there even exist segfaults and protection faults as
if checking for a kernel that is newer than minix era is
necessary. As false positives and negatives for intent to hide even the
oldest and most deprecated "hello world" crud.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Mon, Oct 23, 2023 at 06:48:26PM +0200, Olav Smorholm wrote:
> On Sat, Oct 21, 2023 at 08:52:13PM +0200, Olav Smorholm wrote:
> >
> 
> And call it, or view is it as you may; no trivial task to determine if
> the guix binary bug and crash was useful or not.
> 
> But in the process, while for other things after; starting to study
> dmesg. Bluez and related things that awaken bluetooth kernel subsystems
> is less of an aesthetic problem.
> 
> I react somewhat on PF_ALG especially, weird segfault that calls itself
> xsltproc, and that there even exist segfaults and protection faults as
> if checking for a kernel that is newer than minix era is
> necessary. As false positives and negatives for intent to hide even the
> oldest and most deprecated "hello world" crud.

I'm sure interesting talks can be had:

[73428.629504] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[417] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[419]
[73428.640092] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[420] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[422]
[75861.720983] traps: bonobo-activati[4394] trap int3 ip:7ffff7bf39cf sp:7fffffffbd80 error:0 in libglib-2.0.so.0.7200.3[7ffff7bb7000+88000]
[77216.387681] Bluetooth: Core ver 2.22
[77216.387730] NET: Registered PF_BLUETOOTH protocol family
[77216.387732] Bluetooth: HCI device and connection manager initialized
[77216.387739] Bluetooth: HCI socket layer initialized
[77216.387742] Bluetooth: L2CAP socket layer initialized
[77216.387748] Bluetooth: SCO socket layer initialized
[77917.396492] python[11571]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
[77917.396513] Code: 00 48 83 00 01 c3 0f 1f 40 00 48 89 d0 48 85 d2 74 08 48 83 00 01 c3 0f 1f 00 48 8b 05 11 a7 00 00 48 83 00 01 c3 0f 1f 40 00 <8b> 04 25 00 00 00 00 0f 0b 0f 1f 80 00 00 00 00 48 83 ec 08 48 8b
[77971.483788] python[19206]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Mon, Oct 23, 2023 at 07:03:40PM +0200, Olav Smorholm wrote:
> On Mon, Oct 23, 2023 at 06:48:26PM +0200, Olav Smorholm wrote:
> > On Sat, Oct 21, 2023 at 08:52:13PM +0200, Olav Smorholm wrote:
> > >
> > 
> > And call it, or view is it as you may; no trivial task to determine if
> > the guix binary bug and crash was useful or not.
> > 
> > But in the process, while for other things after; starting to study
> > dmesg. Bluez and related things that awaken bluetooth kernel subsystems
> > is less of an aesthetic problem.
> > 
> > I react somewhat on PF_ALG especially, weird segfault that calls itself
> > xsltproc, and that there even exist segfaults and protection faults as
> > if checking for a kernel that is newer than minix era is
> > necessary. As false positives and negatives for intent to hide even the
> > oldest and most deprecated "hello world" crud.
> 
> I'm sure interesting talks can be had:
> 
> [73428.629504] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[417] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[419]
> [73428.640092] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[420] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[422]
> [75861.720983] traps: bonobo-activati[4394] trap int3 ip:7ffff7bf39cf sp:7fffffffbd80 error:0 in libglib-2.0.so.0.7200.3[7ffff7bb7000+88000]
> [77216.387681] Bluetooth: Core ver 2.22
> [77216.387730] NET: Registered PF_BLUETOOTH protocol family
> [77216.387732] Bluetooth: HCI device and connection manager initialized
> [77216.387739] Bluetooth: HCI socket layer initialized
> [77216.387742] Bluetooth: L2CAP socket layer initialized
> [77216.387748] Bluetooth: SCO socket layer initialized
> [77917.396492] python[11571]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
> [77917.396513] Code: 00 48 83 00 01 c3 0f 1f 40 00 48 89 d0 48 85 d2 74 08 48 83 00 01 c3 0f 1f 00 48 8b 05 11 a7 00 00 48 83 00 01 c3 0f 1f 40 00 <8b> 04 25 00 00 00 00 0f 0b 0f 1f 80 00 00 00 00 48 83 ec 08 48 8b
> [77971.483788] python[19206]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
> 

Not sure if I have point, it's an argument at least.
That the guix binary is a bit of target for the classical problems
involved. And who knowns, maybe one can find a K&R "hello world" string
in a binary as the best and worst of it.

But this is inherently ugly, to see the measures and crud involved, with
awareness of developers that it touch upon sensitive subsystems.
And may very well make it more accessible for study, publications and
discussions if just shafted and most likely fale positives with academic
print og preprint review.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Mon, Oct 23, 2023 at 07:42:02PM +0200, Olav Smorholm wrote:
> On Mon, Oct 23, 2023 at 07:03:40PM +0200, Olav Smorholm wrote:
> > On Mon, Oct 23, 2023 at 06:48:26PM +0200, Olav Smorholm wrote:
> > > On Sat, Oct 21, 2023 at 08:52:13PM +0200, Olav Smorholm wrote:
> > > >
> > > 
> > > And call it, or view is it as you may; no trivial task to determine if
> > > the guix binary bug and crash was useful or not.
> > > 
> > > But in the process, while for other things after; starting to study
> > > dmesg. Bluez and related things that awaken bluetooth kernel subsystems
> > > is less of an aesthetic problem.
> > > 
> > > I react somewhat on PF_ALG especially, weird segfault that calls itself
> > > xsltproc, and that there even exist segfaults and protection faults as
> > > if checking for a kernel that is newer than minix era is
> > > necessary. As false positives and negatives for intent to hide even the
> > > oldest and most deprecated "hello world" crud.
> > 
> > I'm sure interesting talks can be had:
> > 
> > [73428.629504] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[417] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[419]
> > [73428.640092] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[420] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[422]
> > [75861.720983] traps: bonobo-activati[4394] trap int3 ip:7ffff7bf39cf sp:7fffffffbd80 error:0 in libglib-2.0.so.0.7200.3[7ffff7bb7000+88000]
> > [77216.387681] Bluetooth: Core ver 2.22
> > [77216.387730] NET: Registered PF_BLUETOOTH protocol family
> > [77216.387732] Bluetooth: HCI device and connection manager initialized
> > [77216.387739] Bluetooth: HCI socket layer initialized
> > [77216.387742] Bluetooth: L2CAP socket layer initialized
> > [77216.387748] Bluetooth: SCO socket layer initialized
> > [77917.396492] python[11571]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
> > [77917.396513] Code: 00 48 83 00 01 c3 0f 1f 40 00 48 89 d0 48 85 d2 74 08 48 83 00 01 c3 0f 1f 00 48 8b 05 11 a7 00 00 48 83 00 01 c3 0f 1f 40 00 <8b> 04 25 00 00 00 00 0f 0b 0f 1f 80 00 00 00 00 48 83 ec 08 48 8b
> > [77971.483788] python[19206]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
> > 
> 
> Not sure if I have point, it's an argument at least.
> That the guix binary is a bit of target for the classical problems
> involved. And who knowns, maybe one can find a K&R "hello world" string
> in a binary as the best and worst of it.
> 
> But this is inherently ugly, to see the measures and crud involved, with
> awareness of developers that it touch upon sensitive subsystems.
> And may very well make it more accessible for study, publications and
> discussions if just shafted and most likely fale positives with academic
> print og preprint review.
> 

[148083.517777] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[148083.518475] test_regression[21751]: segfault at 0 ip 0000000000000000 sp 00007fffffffb998 error 14 in test_regression[400000+11000] likely on CPU 11 (core 5, socket 0)
[148083.518484] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[148083.519137] test_regression[21752]: segfault at 0 ip 0000000000000000 sp 00007fffffffb998 error 14 in test_regression[400000+11000] likely on CPU 11 (core 5, socket 0)

224051.720066] traps: recentmanager[889] trap int3 ip:7ffff7ee5787 sp:7fffffff5a40 error:0 in libglib-2.0.so.0.7200.3[7ffff7ea7000+88000]

[224450.718378] i915 0000:83:00.0: [drm] *ERROR* Atomic update failure on pipe B (start=174286 end=174287) time 130 us, min 1073, max 1079, scanline start 1071, end 1072
[243753.929744] i915 0000:83:00.0: [drm] *ERROR* Atomic update failure on pipe B (start=1332500 end=1332501) time 155 us, min 1073, max 1079, scanline start 1072, end 1073

The latter of which is icecat i believe.

I at the very least understanding things like CPU pipelines and vector
machines and how they differ. Which can be stated in short terms as
modern CPU's are vector machines inherently. You translate your
instructions into simpler operations that can run faster in the central
logic, or you a fast internal part with several units that translate
onto it and are willing to brute force a soltion if need be.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

Have not seen this in a while, and grateful not to, as it is nice to not
see uncessary segaults. And absolutely do not fall between the luxury,
priviledge, curisty and enthusiasm to dig into it.


[Tue Nov  7 21:52:30 2023] test-recvmsg[14335]: segfault at 0 ip 00007f1130f257d5 sp 00007ffd36b8e670 error 4 in libc.so[7f1130ef3000+62000] likely on CPU 11 (core 5, socket 0)
[Tue Nov  7 21:52:30 2023] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
[Tue Nov  7 21:52:42 2023] test-recvmsg[15831]: segfault at 0 ip 00007fc9c40297d5 sp 00007fffba5c1f10 error 4 in libc.so[7fc9c3ff7000+62000] likely on CPU 1 (core 1, socket 0)
[Tue Nov  7 21:52:42 2023] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
[Thu Nov  9 16:31:51 2023] traps: git[19102] general protection fault ip:4f3320 sp:7fffffff7850 error:0 in git[405000+265000]
[Thu Nov  9 16:31:51 2023] traps: git[19277] general protection fault ip:4f3320 sp:7fffffff7e00 error:0 in git[405000+265000]
[Thu Nov  9 16:31:51 2023] git[19401]: segfault at 40 ip 0000000000639918 sp 00007fffffff6a40 error 4 in git[405000+265000] likely on CPU 12 (core 8, socket 0)
[Thu Nov  9 16:31:51 2023] Code: 24 e0 00 00 00 4c 89 ee 48 83 c3 08 e8 61 ec ff ff 48 3b 5c 24 10 0f 84 5e 07 00 00 49 8b 85 88 00 00 00 48 8b 00 48 8b 34 18 <8b> 4e 40 48 89 b4 24 e0 00 00 00 8d 41 6d 39 e8 0f 8e 72 ff ff ff
[Thu Nov  9 16:31:52 2023] git[19934]: segfault at 40 ip 0000000000639918 sp 00007fffffff6d60 error 4 in git[405000+265000] likely on CPU 1 (core 1, socket 0)
[Thu Nov  9 16:31:52 2023] Code: 24 e0 00 00 00 4c 89 ee 48 83 c3 08 e8 61 ec ff ff 48 3b 5c 24 10 0f 84 5e 07 00 00 49 8b 85 88 00 00 00 48 8b 00 48 8b 34 18 <8b> 4e 40 48 89 b4 24 e0 00 00 00 8d 41 6d 39 e8 0f 8e 72 ff ff ff
[Thu Nov  9 17:46:47 2023] traps: git[5360] general protection fault ip:4f3320 sp:7fffffff7850 error:0 in git[405000+265000]
[Thu Nov  9 17:46:47 2023] traps: git[5483] general protection fault ip:4f3320 sp:7fffffff7e00 error:0 in git[405000+265000]
[Thu Nov  9 17:46:47 2023] git[5579]: segfault at 40 ip 0000000000639918 sp 00007fffffff6a40 error 4 in git[405000+265000] likely on CPU 12 (core 8, socket 0)
[Thu Nov  9 17:46:47 2023] Code: 24 e0 00 00 00 4c 89 ee 48 83 c3 08 e8 61 ec ff ff 48 3b 5c 24 10 0f 84 5e 07 00 00 49 8b 85 88 00 00 00 48 8b 00 48 8b 34 18 <8b> 4e 40 48 89 b4 24 e0 00 00 00 8d 41 6d 39 e8 0f 8e 72 ff ff ff
[Thu Nov  9 17:46:47 2023] git[6014]: segfault at 40 ip 0000000000639918 sp 00007fffffff6d60 error 4 in git[405000+265000] likely on CPU 0 (core 0, socket 0)
[Thu Nov  9 17:46:47 2023] Code: 24 e0 00 00 00 4c 89 ee 48 83 c3 08 e8 61 ec ff ff 48 3b 5c 24 10 0f 84 5e 07 00 00 49 8b 85 88 00 00 00 48 8b 00 48 8b 34 18 <8b> 4e 40 48 89 b4 24 e0 00 00 00 8d 41 6d 39 e8 0f 8e 72 ff ff ff
[Fri Nov 10 03:17:31 2023] derefnull[32137]: segfault at 0 ip 0000000000407351 sp 00007fffffff94a8 error 4 in derefnull[403000+8e000] likely on CPU 6 (core 12, socket 0)
[Fri Nov 10 03:17:31 2023] Code: f8 f6 c3 07 75 13 ff 23 90 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 29 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 b0 58 46 00 49 89 04 24 49 8d 5c 24 f9 48
[Fri Nov 10 03:17:31 2023] traps: divbyzero[32190] trap divide error ip:464cad sp:7fffffff94a8 error:0 in divbyzero[403000+8d000]
[Fri Nov 10 04:26:25 2023] process 'tests/driver/recomp015/Main' started with executable stack
[Fri Nov 10 04:28:56 2023] derefnull[16157]: segfault at 0 ip 00000000004073d1 sp 00007fffffff9478 error 4 in derefnull[403000+94000] likely on CPU 3 (core 5, socket 0)
[Fri Nov 10 04:28:56 2023] Code: 00 00 00 e9 81 65 07 00 90 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 d2 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 d0 a2 46 00 49 89 04 24 49 8d 5c 24 f9 48
[Fri Nov 10 04:28:57 2023] traps: divbyzero[16210] trap divide error ip:46973a sp:7fffffff9478 error:0 in divbyzero[403000+94000]
[Fri Nov 10 05:46:43 2023] derefnull[20162]: segfault at 0 ip 0000000000406359 sp 00007fffffff9208 error 4 in derefnull[402000+a4000] likely on CPU 3 (core 5, socket 0)
[Fri Nov 10 05:46:43 2023] Code: 00 00 00 e9 d1 9b 08 00 90 00 00 00 00 00 00 00 00 1e 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 d2 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 a8 ce 47 00 49 89 04 24 49 8d 5c 24 f9 48
[Fri Nov 10 05:46:44 2023] traps: divbyzero[20218] trap divide error ip:47c277 sp:7fffffff9208 error:0 in divbyzero[402000+a3000]
[Fri Nov 10 07:30:18 2023] derefnull[23071]: segfault at 0 ip 0000000000405f01 sp 00007fffffff91b8 error 4 in derefnull[402000+8b000] likely on CPU 1 (core 1, socket 0)
[Fri Nov 10 07:30:18 2023] Code: 00 00 00 e9 81 0e 07 00 90 00 00 00 00 00 00 00 00 1e 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 d2 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 10 3e 46 00 49 89 04 24 49 8d 5c 24 f9 48
[Fri Nov 10 07:30:20 2023] traps: divbyzero[23125] trap divide error ip:463207 sp:7fffffff91b8 error:0 in divbyzero[402000+8b000]
[Fri Nov 10 09:25:48 2023] derefnull[12645]: segfault at 0 ip 0000000000408989 sp 00007fffffff9108 error 4 in derefnull[403000+93000] likely on CPU 4 (core 8, socket 0)
[Fri Nov 10 09:25:48 2023] Code: f8 f6 c3 07 75 13 ff 23 90 00 00 00 00 00 00 00 00 1e 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 20 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 00 93 46 00 49 89 04 24 49 8d 5c 24 f9 48
[Fri Nov 10 09:25:49 2023] traps: divbyzero[12707] trap divide error ip:46863d sp:7fffffff9108 error:0 in divbyzero[403000+92000]
[Fri Nov 10 09:35:56 2023] T16893[8434]: segfault at 0 ip 00000000004081c9 sp 00007fffffff90f8 error 4 in T16893[403000+8c000] likely on CPU 4 (core 8, socket 0)
[Fri Nov 10 09:35:56 2023] Code: ff 65 f8 66 0f 1f 44 00 00 01 00 00 00 00 00 00 00 1e 00 00 00 d0 14 0a 00 48 c7 45 00 e0 81 40 00 48 8b 5b 0f f6 c3 07 75 17 <ff> 23 0f 1f 44 00 00 01 00 00 00 00 00 00 00 1e 00 00 00 a8 14 0a
[Fri Nov 10 11:30:23 2023] derefnull[10019]: segfault at 0 ip 0000000000409649 sp 00007fffffff9118 error 4 in derefnull[403000+9a000] likely on CPU 4 (core 8, socket 0)
[Fri Nov 10 11:30:23 2023] Code: f8 f6 c3 07 75 13 ff 23 90 00 00 00 00 00 00 00 00 1e 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 20 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 10 df 46 00 49 89 04 24 49 8d 5c 24 f9 48
[Fri Nov 10 11:30:24 2023] traps: divbyzero[10073] trap divide error ip:46d17d sp:7fffffff9118 error:0 in divbyzero[403000+99000]
[Fri Nov 10 23:01:57 2023] test-recvmsg[29536]: segfault at 0 ip 00007f85445df8f5 sp 00007ffd6d583b20 error 4 in libc.so[7f85445ad000+63000] likely on CPU 6 (core 12, socket 0)
[Fri Nov 10 23:01:57 2023] Code: 48 89 c7 e8 9d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
[Fri Nov 10 23:02:09 2023] test-recvmsg[31091]: segfault at 0 ip 00007fb386a788f5 sp 00007ffcc6747dd0 error 4 in libc.so[7fb386a46000+63000] likely on CPU 4 (core 8, socket 0)
[Fri Nov 10 23:02:09 2023] Code: 48 89 c7 e8 9d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
[Sat Nov 11 21:49:22 2023] test-recvmsg[612]: segfault at 0 ip 00007fef6969f7d5 sp 00007ffe5d493920 error 4 in libc.so[7fef6966d000+62000] likely on CPU 4 (core 8, socket 0)
[Sat Nov 11 21:49:22 2023] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
[Sat Nov 11 21:49:34 2023] test-recvmsg[2145]: segfault at 0 ip 00007fc7a04377d5 sp 00007ffc65890850 error 4 in libc.so[7fc7a0405000+62000] likely on CPU 13 (core 9, socket 0)
[Sat Nov 11 21:49:34 2023] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48

On Mon, Oct 23, 2023 at 08:13:29PM +0200, Olav Smorholm wrote:

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Fri, Nov 17, 2023 at 08:37:21PM +0100, Olav Smorholm wrote:
> 
> Have not seen this in a while, and grateful not to, as it is nice to not
> see uncessary segaults. And absolutely do not fall between the luxury,
> priviledge, curisty and enthusiasm to dig into it.
> 
> 
> [Tue Nov  7 21:52:30 2023] test-recvmsg[14335]: segfault at 0 ip 00007f1130f257d5 sp 00007ffd36b8e670 error 4 in libc.so[7f1130ef3000+62000] likely on CPU 11 (core 5, socket 0)
> [Tue Nov  7 21:52:30 2023] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [Tue Nov  7 21:52:42 2023] test-recvmsg[15831]: segfault at 0 ip 00007fc9c40297d5 sp 00007fffba5c1f10 error 4 in libc.so[7fc9c3ff7000+62000] likely on CPU 1 (core 1, socket 0)
> [Tue Nov  7 21:52:42 2023] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [Thu Nov  9 16:31:51 2023] traps: git[19102] general protection fault ip:4f3320 sp:7fffffff7850 error:0 in git[405000+265000]
> [Thu Nov  9 16:31:51 2023] traps: git[19277] general protection fault ip:4f3320 sp:7fffffff7e00 error:0 in git[405000+265000]
> [Thu Nov  9 16:31:51 2023] git[19401]: segfault at 40 ip 0000000000639918 sp 00007fffffff6a40 error 4 in git[405000+265000] likely on CPU 12 (core 8, socket 0)
> [Thu Nov  9 16:31:51 2023] Code: 24 e0 00 00 00 4c 89 ee 48 83 c3 08 e8 61 ec ff ff 48 3b 5c 24 10 0f 84 5e 07 00 00 49 8b 85 88 00 00 00 48 8b 00 48 8b 34 18 <8b> 4e 40 48 89 b4 24 e0 00 00 00 8d 41 6d 39 e8 0f 8e 72 ff ff ff
> [Thu Nov  9 16:31:52 2023] git[19934]: segfault at 40 ip 0000000000639918 sp 00007fffffff6d60 error 4 in git[405000+265000] likely on CPU 1 (core 1, socket 0)
> [Thu Nov  9 16:31:52 2023] Code: 24 e0 00 00 00 4c 89 ee 48 83 c3 08 e8 61 ec ff ff 48 3b 5c 24 10 0f 84 5e 07 00 00 49 8b 85 88 00 00 00 48 8b 00 48 8b 34 18 <8b> 4e 40 48 89 b4 24 e0 00 00 00 8d 41 6d 39 e8 0f 8e 72 ff ff ff
> [Thu Nov  9 17:46:47 2023] traps: git[5360] general protection fault ip:4f3320 sp:7fffffff7850 error:0 in git[405000+265000]
> [Thu Nov  9 17:46:47 2023] traps: git[5483] general protection fault ip:4f3320 sp:7fffffff7e00 error:0 in git[405000+265000]
> [Thu Nov  9 17:46:47 2023] git[5579]: segfault at 40 ip 0000000000639918 sp 00007fffffff6a40 error 4 in git[405000+265000] likely on CPU 12 (core 8, socket 0)
> [Thu Nov  9 17:46:47 2023] Code: 24 e0 00 00 00 4c 89 ee 48 83 c3 08 e8 61 ec ff ff 48 3b 5c 24 10 0f 84 5e 07 00 00 49 8b 85 88 00 00 00 48 8b 00 48 8b 34 18 <8b> 4e 40 48 89 b4 24 e0 00 00 00 8d 41 6d 39 e8 0f 8e 72 ff ff ff
> [Thu Nov  9 17:46:47 2023] git[6014]: segfault at 40 ip 0000000000639918 sp 00007fffffff6d60 error 4 in git[405000+265000] likely on CPU 0 (core 0, socket 0)
> [Thu Nov  9 17:46:47 2023] Code: 24 e0 00 00 00 4c 89 ee 48 83 c3 08 e8 61 ec ff ff 48 3b 5c 24 10 0f 84 5e 07 00 00 49 8b 85 88 00 00 00 48 8b 00 48 8b 34 18 <8b> 4e 40 48 89 b4 24 e0 00 00 00 8d 41 6d 39 e8 0f 8e 72 ff ff ff
> [Fri Nov 10 03:17:31 2023] derefnull[32137]: segfault at 0 ip 0000000000407351 sp 00007fffffff94a8 error 4 in derefnull[403000+8e000] likely on CPU 6 (core 12, socket 0)
> [Fri Nov 10 03:17:31 2023] Code: f8 f6 c3 07 75 13 ff 23 90 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 29 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 b0 58 46 00 49 89 04 24 49 8d 5c 24 f9 48
> [Fri Nov 10 03:17:31 2023] traps: divbyzero[32190] trap divide error ip:464cad sp:7fffffff94a8 error:0 in divbyzero[403000+8d000]
> [Fri Nov 10 04:26:25 2023] process 'tests/driver/recomp015/Main' started with executable stack
> [Fri Nov 10 04:28:56 2023] derefnull[16157]: segfault at 0 ip 00000000004073d1 sp 00007fffffff9478 error 4 in derefnull[403000+94000] likely on CPU 3 (core 5, socket 0)
> [Fri Nov 10 04:28:56 2023] Code: 00 00 00 e9 81 65 07 00 90 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 d2 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 d0 a2 46 00 49 89 04 24 49 8d 5c 24 f9 48
> [Fri Nov 10 04:28:57 2023] traps: divbyzero[16210] trap divide error ip:46973a sp:7fffffff9478 error:0 in divbyzero[403000+94000]
> [Fri Nov 10 05:46:43 2023] derefnull[20162]: segfault at 0 ip 0000000000406359 sp 00007fffffff9208 error 4 in derefnull[402000+a4000] likely on CPU 3 (core 5, socket 0)
> [Fri Nov 10 05:46:43 2023] Code: 00 00 00 e9 d1 9b 08 00 90 00 00 00 00 00 00 00 00 1e 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 d2 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 a8 ce 47 00 49 89 04 24 49 8d 5c 24 f9 48
> [Fri Nov 10 05:46:44 2023] traps: divbyzero[20218] trap divide error ip:47c277 sp:7fffffff9208 error:0 in divbyzero[402000+a3000]
> [Fri Nov 10 07:30:18 2023] derefnull[23071]: segfault at 0 ip 0000000000405f01 sp 00007fffffff91b8 error 4 in derefnull[402000+8b000] likely on CPU 1 (core 1, socket 0)
> [Fri Nov 10 07:30:18 2023] Code: 00 00 00 e9 81 0e 07 00 90 00 00 00 00 00 00 00 00 1e 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 d2 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 10 3e 46 00 49 89 04 24 49 8d 5c 24 f9 48
> [Fri Nov 10 07:30:20 2023] traps: divbyzero[23125] trap divide error ip:463207 sp:7fffffff91b8 error:0 in divbyzero[402000+8b000]
> [Fri Nov 10 09:25:48 2023] derefnull[12645]: segfault at 0 ip 0000000000408989 sp 00007fffffff9108 error 4 in derefnull[403000+93000] likely on CPU 4 (core 8, socket 0)
> [Fri Nov 10 09:25:48 2023] Code: f8 f6 c3 07 75 13 ff 23 90 00 00 00 00 00 00 00 00 1e 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 20 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 00 93 46 00 49 89 04 24 49 8d 5c 24 f9 48
> [Fri Nov 10 09:25:49 2023] traps: divbyzero[12707] trap divide error ip:46863d sp:7fffffff9108 error:0 in divbyzero[403000+92000]
> [Fri Nov 10 09:35:56 2023] T16893[8434]: segfault at 0 ip 00000000004081c9 sp 00007fffffff90f8 error 4 in T16893[403000+8c000] likely on CPU 4 (core 8, socket 0)
> [Fri Nov 10 09:35:56 2023] Code: ff 65 f8 66 0f 1f 44 00 00 01 00 00 00 00 00 00 00 1e 00 00 00 d0 14 0a 00 48 c7 45 00 e0 81 40 00 48 8b 5b 0f f6 c3 07 75 17 <ff> 23 0f 1f 44 00 00 01 00 00 00 00 00 00 00 1e 00 00 00 a8 14 0a
> [Fri Nov 10 11:30:23 2023] derefnull[10019]: segfault at 0 ip 0000000000409649 sp 00007fffffff9118 error 4 in derefnull[403000+9a000] likely on CPU 4 (core 8, socket 0)
> [Fri Nov 10 11:30:23 2023] Code: f8 f6 c3 07 75 13 ff 23 90 00 00 00 00 00 00 00 00 1e 00 00 00 00 00 00 00 49 83 c4 10 4d 3b a5 58 03 00 00 77 20 48 8b 43 07 <48> 8b 00 49 c7 44 24 f8 10 df 46 00 49 89 04 24 49 8d 5c 24 f9 48
> [Fri Nov 10 11:30:24 2023] traps: divbyzero[10073] trap divide error ip:46d17d sp:7fffffff9118 error:0 in divbyzero[403000+99000]
> [Fri Nov 10 23:01:57 2023] test-recvmsg[29536]: segfault at 0 ip 00007f85445df8f5 sp 00007ffd6d583b20 error 4 in libc.so[7f85445ad000+63000] likely on CPU 6 (core 12, socket 0)
> [Fri Nov 10 23:01:57 2023] Code: 48 89 c7 e8 9d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [Fri Nov 10 23:02:09 2023] test-recvmsg[31091]: segfault at 0 ip 00007fb386a788f5 sp 00007ffcc6747dd0 error 4 in libc.so[7fb386a46000+63000] likely on CPU 4 (core 8, socket 0)
> [Fri Nov 10 23:02:09 2023] Code: 48 89 c7 e8 9d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [Sat Nov 11 21:49:22 2023] test-recvmsg[612]: segfault at 0 ip 00007fef6969f7d5 sp 00007ffe5d493920 error 4 in libc.so[7fef6966d000+62000] likely on CPU 4 (core 8, socket 0)
> [Sat Nov 11 21:49:22 2023] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [Sat Nov 11 21:49:34 2023] test-recvmsg[2145]: segfault at 0 ip 00007fc7a04377d5 sp 00007ffc65890850 error 4 in libc.so[7fc7a0405000+62000] likely on CPU 13 (core 9, socket 0)
> [Sat Nov 11 21:49:34 2023] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> 
Binary or what not, I boldly take this as community confirmation of the
bug report, and admittance of usage. With a huge what-if, and if-only-if
where lines to do not cross internally in non-profit or for profit
organisation with isolated soap boax requests and issues.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Fri, Nov 17, 2023 at 08:55:08PM +0100, Olav Smorholm wrote:
> Binary or what not, I boldly take this as community confirmation of the
> bug report, and admittance of usage. With a huge what-if, and if-only-if
> where lines to do not cross internally in non-profit or for profit
> organisation with isolated soap boax requests and issues.

Now, Imagine you are me:
https://ieeexplore.ieee.org/author/37088682708

Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
With no high school degree.
And while with on resolution to TBI in inferior parietal lobe.
I do whole genome sequencing and the west atlantic trade route from
Norway in early Viking age shows up at gedmatc.com, I'm 0.1% lebanese
jew, and closer to 3% moroccan in top 10 admixes, and it includes
Saami mtDNA in the Berber ancestral population. If it is like water,
some social borders and structures I may naturally sail it.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> With no high school degree.

I will be captain obvious for something I'm not certain about, but I am
in a matter of ways in dialogue with Intel Liaoson to CERN.
That IT department of Intel, they also did and were interest in
frameworks I were interested in, during early interaction in OpenLab.
    Something implicit may need to be said, there is a division in
semiconductor companies between researchers and services.
The latter cant ask, and the former cant request work that they just
can't do easily or quickly.

So iif I pretend to be RMS here, it's one thing over the other, and
provide commenty for open assembly code if need be.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Fri, Nov 17, 2023 at 09:40:38PM +0100, Olav Smorholm wrote:
> On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> > Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> > With no high school degree.
> 
> I will be captain obvious for something I'm not certain about, but I am
> in a matter of ways in dialogue with Intel Liaoson to CERN.
> That IT department of Intel, they also did and were interest in
> frameworks I were interested in, during early interaction in OpenLab.
>     Something implicit may need to be said, there is a division in
> semiconductor companies between researchers and services.
> The latter cant ask, and the former cant request work that they just
> can't do easily or quickly.
> 
> So iif I pretend to be RMS here, it's one thing over the other, and
> provide commenty for open assembly code if need be.
> 
In other words, there is a definition of the number line that involves
integers, fractions and complex numbers with no negative numbers.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Fri, Nov 17, 2023 at 10:24:01PM +0100, Olav Smorholm wrote:
> On Fri, Nov 17, 2023 at 09:40:38PM +0100, Olav Smorholm wrote:
> > On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> > > Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> > > With no high school degree.
> > 
> > I will be captain obvious for something I'm not certain about, but I am
> > in a matter of ways in dialogue with Intel Liaoson to CERN.
> > That IT department of Intel, they also did and were interest in
> > frameworks I were interested in, during early interaction in OpenLab.
> >     Something implicit may need to be said, there is a division in
> > semiconductor companies between researchers and services.
> > The latter cant ask, and the former cant request work that they just
> > can't do easily or quickly.
> > 
> > So iif I pretend to be RMS here, it's one thing over the other, and
> > provide commenty for open assembly code if need be.
> > 
> In other words, there is a definition of the number line that involves
> integers, fractions and complex numbers with no negative numbers.


https://www.internationalgenome.org/faq/what-do-the-population-codes-mean/

I struggled with this one, I am in some models more cloesly related to
CEU than the rest of Scandinavia. You are welcome, to this dsicprenacy
and divide. It does mean, native with ancestry.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Fri, Nov 17, 2023 at 11:59:45PM +0100, Olav Smorholm wrote:
> On Fri, Nov 17, 2023 at 10:24:01PM +0100, Olav Smorholm wrote:
> > On Fri, Nov 17, 2023 at 09:40:38PM +0100, Olav Smorholm wrote:
> > > On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> > > > Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> > > > With no high school degree.
> > > 
> > > I will be captain obvious for something I'm not certain about, but I am
> > > in a matter of ways in dialogue with Intel Liaoson to CERN.
> > > That IT department of Intel, they also did and were interest in
> > > frameworks I were interested in, during early interaction in OpenLab.
> > >     Something implicit may need to be said, there is a division in
> > > semiconductor companies between researchers and services.
> > > The latter cant ask, and the former cant request work that they just
> > > can't do easily or quickly.
> > > 
> > > So iif I pretend to be RMS here, it's one thing over the other, and
> > > provide commenty for open assembly code if need be.
> > > 
> > In other words, there is a definition of the number line that involves
> > integers, fractions and complex numbers with no negative numbers.
> 
> 
> https://www.internationalgenome.org/faq/what-do-the-population-codes-mean/
> 
> I struggled with this one, I am in some models more cloesly related to
> CEU than the rest of Scandinavia. You are welcome, to this dsicprenacy
> and divide. It does mean, native with ancestry.

And I am borderline, and ifit isn't enough comfort.
I have peggeed https://surfer.nmr.mgh.harvard.edu/ as possibly the best
place to get a TBI diagnostics, but I am being blocked by the front desk
at MGH.

Suck on that.

bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)

[Olav Smorholm]

On Sat, Nov 18, 2023 at 12:16:54AM +0100, Olav Smorholm wrote:
> On Fri, Nov 17, 2023 at 11:59:45PM +0100, Olav Smorholm wrote:
> > On Fri, Nov 17, 2023 at 10:24:01PM +0100, Olav Smorholm wrote:
> > > On Fri, Nov 17, 2023 at 09:40:38PM +0100, Olav Smorholm wrote:
> > > > On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> > > > > Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> > > > > With no high school degree.
> > > > 
> > > > I will be captain obvious for something I'm not certain about, but I am
> > > > in a matter of ways in dialogue with Intel Liaoson to CERN.
> > > > That IT department of Intel, they also did and were interest in
> > > > frameworks I were interested in, during early interaction in OpenLab.
> > > >     Something implicit may need to be said, there is a division in
> > > > semiconductor companies between researchers and services.
> > > > The latter cant ask, and the former cant request work that they just
> > > > can't do easily or quickly.
> > > > 
> > > > So iif I pretend to be RMS here, it's one thing over the other, and
> > > > provide commenty for open assembly code if need be.
> > > > 
> > > In other words, there is a definition of the number line that involves
> > > integers, fractions and complex numbers with no negative numbers.
> > 
> > 
> > https://www.internationalgenome.org/faq/what-do-the-population-codes-mean/
> > 
> > I struggled with this one, I am in some models more cloesly related to
> > CEU than the rest of Scandinavia. You are welcome, to this dsicprenacy
> > and divide. It does mean, native with ancestry.
> 
> And I am borderline, and ifit isn't enough comfort.
> I have peggeed https://surfer.nmr.mgh.harvard.edu/ as possibly the best
> place to get a TBI diagnostics, but I am being blocked by the front desk
> at MGH.
> 
> Suck on that.
> 
And rantn and digression set aside.
I will have this screwed.
You don't win any wards with a piece of shit build systems from
disregard of giants and titans that made is possible.

Wnile publications like mine serve as insurance against medical
malpractice.

bug#66610: potrace, po4a; guix bug, complete console output

[Maxim Cournoyer]

Hi Olav,

[...]

Thanks for the initial bug report about a po4a non reproducible segfault
(did I get this right?).

Please refrain from posting unrelated things to this report, as that's
lowering the signal to noise ratio and making it less likely that
someone is interested in reading your future replies.

-- 
Thanks,
Maxim