From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24764@debbugs.gnu.org
Subject: bug#24764: 25.1.50; Another crash in automatic gc
Date: Sun, 23 Oct 2016 12:53:32 +0200 [thread overview]
Message-ID: <87wpgzl4k3.fsf@web.de> (raw)
In-Reply-To: <83shrnnz4s.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 23 Oct 2016 13:22:27 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Could it be that you've upgraded your libc since that previous build?
That's likely. Here is my aptitude's term.log, from Oct/1, `occurre'd
for "\_<libc", with some irrelevant lines removed - I guess that it
means "yes":
130 matches in 129 lines for "\_<libc" in buffer: term.log
9:Unpacking libc-l10n (2.24-3) over (2.23-5) ...
13:Unpacking libc6-i386 (2.24-3) over (2.23-5) ...
15:Unpacking libc-dev-bin (2.24-3) over (2.23-5) ...
17:Unpacking libc6-dev:amd64 (2.24-3) over (2.23-5) ...
19:Unpacking libc6-dev-i386 (2.24-3) over (2.23-5) ...
21:Unpacking libc6-dev-x32 (2.24-3) over (2.23-5) ...
23:Unpacking libc6-x32 (2.24-3) over (2.23-5) ...
28:Setting up libc6:amd64 (2.24-3) ...
40:Unpacking libc-bin (2.24-3) over (2.23-5) ...
41:Setting up libc-bin (2.24-3) ...
81:Unpacking libcomerr2:amd64 (1.43.3-1) over (1.43.1-1) ...
82:Setting up libcomerr2:amd64 (1.43.3-1) ...
382:Setting up libc6-x32 (2.24-3) ...
404:Setting up libc6-i386 (2.24-3) ...
426:Setting up libc-l10n (2.24-3) ...
432:Setting up libc-dev-bin (2.24-3) ...
437:Setting up libc6-dev:amd64 (2.24-3) ...
485:Setting up libc6-dev-i386 (2.24-3) ...
487:Setting up libc6-dev-x32 (2.24-3) ...
631:Selecting previously unselected package libcgal12:amd64.
633:Unpacking libcgal12:amd64 (4.9-1) ...
641:Removing libcgal11v5:amd64 (4.8.1-1+b1) ...
713:Setting up libcgal12:amd64 (4.9-1) ...
857:Unpacking libcupsfilters1:amd64 (1.11.4-1) over (1.10.0-1) ...
898:Setting up libcupsfilters1:amd64 (1.11.4-1) ...
1487:Unpacking libcaja-extension1:amd64 (1.16.0-1) over (1.14.2-1) ...
1618:Setting up libcaja-extension1:amd64 (1.16.0-1) ...
1734:Unpacking libcupscgi1:amd64 (2.2.1-1) over (2.2.0-2) ...
1736:Unpacking libcupsimage2:amd64 (2.2.1-1) over (2.2.0-2) ...
1746:Unpacking libcupsppdc1:amd64 (2.2.1-1) over (2.2.0-2) ...
1748:Unpacking libcupsmime1:amd64 (2.2.1-1) over (2.2.0-2) ...
1760:Unpacking libcups2:amd64 (2.2.1-1) over (2.2.0-2) ...
1835:Setting up libcups2:amd64 (2.2.1-1) ...
1838:Setting up libcupsmime1:amd64 (2.2.1-1) ...
1842:Setting up libcupsppdc1:amd64 (2.2.1-1) ...
1843:Setting up libcupsimage2:amd64 (2.2.1-1) ...
1845:Setting up libcupscgi1:amd64 (2.2.1-1) ...
2136:Unpacking libcryptsetup4:amd64 (2:1.7.2-3) over (2:1.7.0-2) ...
2137:Setting up libcryptsetup4:amd64 (2:1.7.2-3) ...
2701:Unpacking libcryptsetup4:amd64 (2:1.7.2-4) over (2:1.7.2-3) ...
2702:Setting up libcryptsetup4:amd64 (2:1.7.2-4) ...
2705:Unpacking libcgal12:amd64 (4.9-1+b1) over (4.9-1) ...
2706:Setting up libcgal12:amd64 (4.9-1+b1) ...
2959:Unpacking libcc1-0:amd64 (6.2.0-6) over (6.1.1-11) ...
2973:Unpacking libcilkrts5:amd64 (6.2.0-6) over (6.1.1-11) ...
3051:Setting up libcc1-0:amd64 (6.2.0-6) ...
3058:Setting up libcilkrts5:amd64 (6.2.0-6) ...
3125:Unpacking libcrypto++-dev (5.6.4-1) over (5.6.3-8) ...
3127:Unpacking libcrypto++6 (5.6.4-1) over (5.6.3-8) ...
3133:Setting up libcrypto++6 (5.6.4-1) ...
3134:Setting up libcrypto++-dev (5.6.4-1) ...
> That could mean that previously you didn't use ralloc.c, whereas now
> you do.
Is it worth to try to downgrade libc stuff to stable?
Michael.
next prev parent reply other threads:[~2016-10-23 10:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 9:38 bug#24764: 25.1.50; Another crash in automatic gc Michael Heerdegen
2016-10-22 10:05 ` Eli Zaretskii
2016-10-22 11:41 ` Andreas Schwab
2016-10-22 12:01 ` Eli Zaretskii
2016-10-22 12:21 ` Eli Zaretskii
2016-10-22 14:05 ` Michael Heerdegen
2016-10-22 14:10 ` Eli Zaretskii
2016-10-22 14:43 ` Michael Heerdegen
2016-10-22 15:08 ` Eli Zaretskii
2016-10-22 18:25 ` Michael Heerdegen
2016-10-22 18:35 ` Eli Zaretskii
2016-10-23 9:06 ` Michael Heerdegen
2016-10-23 9:32 ` Eli Zaretskii
2016-10-23 10:22 ` Eli Zaretskii
2016-10-23 10:53 ` Michael Heerdegen [this message]
2016-10-23 12:06 ` Eli Zaretskii
2016-10-23 10:49 ` Michael Heerdegen
2016-10-23 10:24 ` Eli Zaretskii
2016-10-23 11:00 ` Michael Heerdegen
2016-10-23 12:08 ` Eli Zaretskii
2016-10-23 13:57 ` Eli Zaretskii
2016-10-23 15:53 ` Michael Heerdegen
2016-10-23 16:37 ` Michael Heerdegen
2016-10-23 17:01 ` Eli Zaretskii
2016-10-25 14:37 ` Michael Heerdegen
2016-10-25 16:46 ` Eli Zaretskii
2016-10-25 17:21 ` Michael Heerdegen
2016-10-25 18:17 ` Eli Zaretskii
2016-10-27 16:40 ` Michael Heerdegen
2016-10-27 17:18 ` Eli Zaretskii
2016-11-07 3:38 ` Eli Zaretskii
2016-11-07 11:36 ` Michael Heerdegen
2016-10-22 12:36 ` Eli Zaretskii
2016-10-22 13:54 ` Michael Heerdegen
2016-10-22 14:12 ` Michael Heerdegen
2016-10-22 14:24 ` Eli Zaretskii
2016-10-22 14:13 ` Eli Zaretskii
2016-10-23 9:32 ` Michael Heerdegen
2016-10-22 14:37 ` npostavs
2016-10-22 14:38 ` Eli Zaretskii
2016-10-22 14:51 ` Michael Heerdegen
2016-10-22 15:25 ` Eli Zaretskii
2016-10-22 15:33 ` Eli Zaretskii
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=87wpgzl4k3.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=24764@debbugs.gnu.org \
--cc=eliz@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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.