unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Olav Smorholm <olavks@gmail.com>
To: 66610@debbugs.gnu.org
Subject: bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)
Date: Sat, 21 Oct 2023 20:52:11 +0200	[thread overview]
Message-ID: <yc7ditmczudqllm4bbctymgm2vixl7k7266xzrwfp5yetgfwbh@yjs4siyoz34t> (raw)
In-Reply-To: <j5kmm34mxgdd4qvslwk4kr36ffy4uh4ljwiqxpwuugap75mwtz@jzbujq42tcbb>

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.




  reply	other threads:[~2023-10-21 18:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 14:00 bug#66610: potrace, po4a; guix bug, complete console output Olav Smorholm
     [not found] ` <handler.66610.B.169764205314809.ack@debbugs.gnu.org>
2023-10-18 15:34   ` bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output) Olav Smorholm
2023-10-18 21:21     ` Olav Smorholm
2023-10-19 13:04       ` Olav Smorholm
2023-10-19 16:29         ` Olav Smorholm
2023-10-19 22:36           ` Olav Smorholm
2023-10-21 14:57             ` Olav Smorholm
2023-10-21 17:12               ` Olav Smorholm
2023-10-21 18:29                 ` Olav Smorholm
2023-10-21 18:52                   ` Olav Smorholm [this message]
2023-10-23 16:48                     ` Olav Smorholm
2023-10-23 17:03                       ` Olav Smorholm
2023-10-23 17:42                         ` Olav Smorholm
2023-10-23 18:13                           ` Olav Smorholm
2023-11-17 19:37                             ` Olav Smorholm
2023-11-17 19:55                               ` Olav Smorholm
2023-11-17 20:16                                 ` Olav Smorholm
2023-11-17 20:40                                   ` Olav Smorholm
2023-11-17 21:24                                     ` Olav Smorholm
2023-11-17 22:59                                       ` Olav Smorholm
2023-11-17 23:16                                         ` Olav Smorholm
2023-12-08  0:17                                           ` Olav Smorholm
2023-12-19  5:20                                             ` bug#66610: potrace, po4a; guix bug, complete console output Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yc7ditmczudqllm4bbctymgm2vixl7k7266xzrwfp5yetgfwbh@yjs4siyoz34t \
    --to=olavks@gmail.com \
    --cc=66610@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).