From: Gregor Zattler <telegraph@gmx.net>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: build fails with segmentation fault, how to find the reason?
Date: Sat, 28 Feb 2015 12:18:28 +0100 [thread overview]
Message-ID: <20150228111828.GA18641@boo.workgroup> (raw)
In-Reply-To: <vr385qj2m9.fsf@fencepost.gnu.org>
Hi Glenn,
* Glenn Morris <rgm@gnu.org> [27. Feb. 2015]:
> Gregor Zattler wrote:
>
>> fault (see below). Since nobody else complained here or on
>> emacs-devel I assume this is a local problem on my debian/jessie
>> system.
>
> Or maybe they just know to where to report bugs? :)
> Ie to the bug list, not the help or devel lists.
> I guess you are on a 32-bit system:
right, yes, thanks.
> http://debbugs.gnu.org/19959
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
prev parent reply other threads:[~2015-02-28 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 23:55 build fails with segmentation fault, how to find the reason? Gregor Zattler
2015-02-28 0:34 ` Glenn Morris
2015-02-28 11:18 ` Gregor Zattler [this message]
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150228111828.GA18641@boo.workgroup \
--to=telegraph@gmx.net \
--cc=help-gnu-emacs@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.
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).