From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: reproducable orgmode edit crashes emacs..have backtrace..where to report? Date: Fri, 09 Dec 2016 14:09:28 +0000 Message-ID: References: <871sxh8col.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113ad4e21c059505433a4e8b Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45265) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cFLtD-0001yD-Hh for emacs-orgmode@gnu.org; Fri, 09 Dec 2016 09:11:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cFLt9-0004Gi-98 for emacs-orgmode@gnu.org; Fri, 09 Dec 2016 09:11:07 -0500 Received: from mail-ua0-f172.google.com ([209.85.217.172]:34778) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cFLt9-0004F3-36 for emacs-orgmode@gnu.org; Fri, 09 Dec 2016 09:11:03 -0500 Received: by mail-ua0-f172.google.com with SMTP id 51so18158045uai.1 for ; Fri, 09 Dec 2016 06:10:41 -0800 (PST) In-Reply-To: <871sxh8col.fsf@ucl.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Eric S Fraga , Xebar Saram Cc: emacs-org list --001a113ad4e21c059505433a4e8b Content-Type: text/plain; charset=UTF-8 On Fri, Dec 9, 2016, 8:51 AM Eric S Fraga wrote: > On Friday, 9 Dec 2016 at 11:33, Xebar Saram wrote: > > Maybe using M-x report-emacs-bug RET? > Yup, filing a bug report is the best way in this case. Emacs is not supposed to crash no matter what the user or any package does in the elisp land. M-x report-emacs-bug will also provide the devs with info like your emacs version, which can be useful to debug this crash. Also provide a recipe in that bug report on how to recreate that crash from an emacs -Q session. It would be useful also to elaborate on what change you did you think started these crashes to happen... Updating Emacs, updating org, both, or something else? > -- Kaushal Modi --001a113ad4e21c059505433a4e8b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Fri, Dec 9, 2016, 8:= 51 AM Eric S Fraga <e.fraga@ucl.ac.= uk> wrote:
On Friday,=C2=A0 = 9 Dec 2016 at 11:33, Xebar Saram wrote:

Maybe using M-x report-emacs-bug RET?
<= /div>

Yup, filing a bug report is the best way in this c= ase. Emacs is not supposed to crash no matter what the user or any package = does in the elisp land.=C2=A0

M-x report-emacs-bug= will also provide the devs with info like your emacs version, which can be= useful to debug this crash. Also provide a recipe in that bug report on ho= w to recreate that crash from an emacs -Q session. It would be useful also = to elaborate on what change you did you think started these crashes to happ= en... Updating Emacs, updating org, both, or something else?
--

Kaushal Modi

--001a113ad4e21c059505433a4e8b--