From: Kaushal Modi <kaushal.modi@gmail.com>
To: Michael Ax <michaelax@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: segfault when org-ellipsis is empty
Date: Mon, 26 Jun 2017 18:20:42 +0000 [thread overview]
Message-ID: <CAFyQvY3z2WVEYzueag52r=Y3HieSuJVDvURFFqy47+mYN9aE=g@mail.gmail.com> (raw)
In-Reply-To: <6b6ee521-a482-0377-6f46-23c91365bee4@gMail.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
On Mon, Jun 26, 2017 at 2:10 PM Michael Ax <michaelax@gmail.com> wrote:
> Hello, I trust that this is the right place to report a segfault.
>
The right place to report emacs segfault (whether caused by another package
or not) would be by M-x report-emacs-bug from within emacs. If you haven't
set up to send emails from within emacs (I haven't), then copy the To email
address, email subject and the generated email body and email it it using
your default email client.
> Using whatever is current in debian 9, emacs segfaults
> from a minimum setup when using an empty string for org-ellipsis.
>
> Here's how to reproduce it:
>
> > emacs -Q
>
> (setq org-ellipsis "") C-x C-e
> (org-mode) C-x C-e
> * asd
> ** def C-p tab < and boom
>
> Cool!
I can recreate that error on emacs master + org 9.0.9.
> My emacs isn't built from sources, so the ftrace/backtrace
> is meaningless for the "Fatal error 11: Segmentation fault"
>
> If there is a bugtracker and there always is a bugtracker,
> then my apologies in case this has already been dealt with.
>
> m
>
Once you send that bug report, you will get a debbugs number. Please post
that number in this thread (for people curious about this bug like me).
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2315 bytes --]
next prev parent reply other threads:[~2017-06-26 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 18:09 segfault when org-ellipsis is empty Michael Ax
2017-06-26 18:20 ` Kaushal Modi [this message]
2017-06-26 20:18 ` Nicolas Goaziou
2017-06-26 21:13 ` Kaushal Modi
2017-06-26 21:42 ` Nicolas Goaziou
2017-06-26 22:46 ` Michael Ax
2017-06-27 16:26 ` Kaushal Modi
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='CAFyQvY3z2WVEYzueag52r=Y3HieSuJVDvURFFqy47+mYN9aE=g@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=michaelax@gmail.com \
/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.