all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: 18392@debbugs.gnu.org, 759400-forwarded@bugs.debian.org,
	Stefan Monnier <monnier@IRO.UMontreal.CA>,
	David Bremner <bremner@debian.org>,
	759400@bugs.debian.org
Subject: bug#18392: Bug#759400: emacs24-nox: segfault when saving emacs lisp file
Date: Sat, 26 Dec 2015 17:05:34 +0100	[thread overview]
Message-ID: <87a8oxry9d.fsf@gnus.org> (raw)
In-Reply-To: <87mwagh1wy.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Wed, 03 Sep 2014 15:41:49 -0500")

Rob Browning <rlb@defaultvalue.org> writes:

> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>
>> Could you check whether the same problem shows up for the 24.4 pretest
>> (i.e. 24.3.93)?  Also, worthwhile would be to test to see if building
>> with different optimization settings changes the result.
>
> Of course, I should have done this initially, but I just tried a clean
> emacs-24.4.tar.xz build, and assuming I didn't make any mistakes, that
> worked fine, so I need to investigate further on the Debian side.
>
> Thanks for the help.

Ok; closing this report in the Emacs bug tracker.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2015-12-26 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140827001632.24080.53245.reportbug@maritornes.cs.unb.ca>
     [not found] ` <20140827082930.GC1371@sid.nuvreauspam>
2014-09-03  3:16   ` bug#18392: Bug#759400: emacs24-nox: segfault when saving emacs lisp file Rob Browning
2014-09-03 13:23     ` Stefan Monnier
2014-09-03 18:51       ` David Bremner
2014-09-03 20:41       ` Rob Browning
2015-12-26 16:05         ` Lars Ingebrigtsen [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

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

  git send-email \
    --in-reply-to=87a8oxry9d.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18392@debbugs.gnu.org \
    --cc=759400-forwarded@bugs.debian.org \
    --cc=759400@bugs.debian.org \
    --cc=bremner@debian.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=rlb@defaultvalue.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.