From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25442@debbugs.gnu.org
Subject: bug#25442: stacktrace
Date: Sun, 15 Jan 2017 23:36:34 +0100 [thread overview]
Message-ID: <87shok9ci5.fsf@gnu.org> (raw)
In-Reply-To: <87k29wgj7b.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 15 Jan 2017 21:30:00 +0100")
Ludovic Courtès writes:
>> I'm not sure how to continue here; I built Emacs from GIT and there the
>> problem is not present. Looking at the diff from 25.1 until HEAD I do
>> not see any obvious patches, neither does the git log point me to one.
>
> So the question is whether this bug is introduced by our packaging or
> whether it’s an upstream bug.
Yes.
> Perhaps you could build with (warning! this command does not
> authenticate the tarball it downloads):
>
> guix package -i emacs emacs:debug \
> --with-source=ftp://alpha.gnu.org/gnu/emacs/emacs-25.1.91.tar.xz
guix package -i emacs emacs:debug \
--with-source=ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-25.1.91.tar.xz
inserted /pretest here
> I’m afraid that’s all I can suggest now.
That's a good suggestion. I have tried this and the bug is also gone
here, with our packaging. So apparently it has been fixed upstream.
Thanks!
Greetings,
Jan
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next prev parent reply other threads:[~2017-01-15 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 21:21 bug#25442: Emacs compilation buffer segfault Jan Nieuwenhuizen
2017-01-14 16:06 ` bug#25442: stacktrace Jan Nieuwenhuizen
2017-01-14 17:24 ` Ludovic Courtès
2017-01-14 19:56 ` Jan Nieuwenhuizen
2017-01-15 20:30 ` Ludovic Courtès
2017-01-15 22:36 ` Jan Nieuwenhuizen [this message]
2017-09-30 7:36 ` Jan Nieuwenhuizen
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=87shok9ci5.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=25442@debbugs.gnu.org \
--cc=ludo@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).