From: Olav Smorholm <olavks@gmail.com>
To: 66610@debbugs.gnu.org
Subject: bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)
Date: Mon, 23 Oct 2023 19:03:39 +0200 [thread overview]
Message-ID: <csrbbut4sdg2c5ajnbgv645begi55kkk2k3npbmmvctvvmrmli@knet3re473mw> (raw)
In-Reply-To: <iu6hm7kknn7nyatjjjfjmt4nlyshed6cb2gqkipygt7xh6vwnd@e3ejh3ru23vb>
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)
next prev parent reply other threads:[~2023-10-23 17:04 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
2023-10-23 16:48 ` Olav Smorholm
2023-10-23 17:03 ` Olav Smorholm [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=csrbbut4sdg2c5ajnbgv645begi55kkk2k3npbmmvctvvmrmli@knet3re473mw \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.