From: Yagnesh Raghava Yakkala <hi@yagnesh.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16070@debbugs.gnu.org
Subject: bug#16070: 24.3.50; Crash, Emacs fatal error: assertion failed: c->buffer_beg <= start && end <= c->buffer_end
Date: Sat, 07 Dec 2013 14:53:03 +0900 [thread overview]
Message-ID: <87a9gd8aww.fsf@yagnesh.org> (raw)
In-Reply-To: <83haam103l.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Dec 2013 17:16:14 +0200")
Hello Eli,
On Dec 07 2013, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Yagnesh Raghava Yakkala <hi@yagnesh.org>
>> Cc: 16070@debbugs.gnu.org
>> Date: Fri, 06 Dec 2013 21:39:52 +0900
>>
>> > I guess this crash doesn't happen with every Org file, because I just
>> > tried and it didn't crash. Could you post the shortest Org file that
>> > causes the crash, and also tell at what position in the file to try to
>> > cycle visibility?
>>
>> Please see cut down version of my org file.
>>
>> When opened attached org as follows, it automatically crashes on my system.
>> emacs -Q test.org -eval "(set-buffer-multibyte nil)"
>
> Thanks. That particular crash is fixed in trunk revision 115399,
Thanks and I can confirm.
> (did you also toggle buffer's multibyteness there, after visiting the
> file?).
Yes.
> If the problem is not entirely fixed, please show the recipe to reproduce
> the problem.
I can't reproduce original problem now. I think we can close this bug now.
Thanks.,
--
ఎందరో మహానుభావులు అందరికి వందనములు.
YYR
next prev parent reply other threads:[~2013-12-07 5:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 10:43 bug#16070: 24.3.50; Crash, Emacs fatal error: assertion failed: c->buffer_beg <= start && end <= c->buffer_end Yagnesh Raghava Yakkala
2013-12-06 10:51 ` Yagnesh Raghava Yakkala
2013-12-06 11:23 ` Eli Zaretskii
2013-12-06 11:28 ` Eli Zaretskii
2013-12-06 12:39 ` Yagnesh Raghava Yakkala
2013-12-06 15:16 ` Eli Zaretskii
2013-12-07 5:53 ` Yagnesh Raghava Yakkala [this message]
2013-12-07 8:35 ` Eli Zaretskii
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=87a9gd8aww.fsf@yagnesh.org \
--to=hi@yagnesh.org \
--cc=16070@debbugs.gnu.org \
--cc=eliz@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/emacs.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).