From: vordoo <vordoo@yahoo.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: 33222@debbugs.gnu.org
Subject: bug#33222: Crash when visiting an org file from within Dired.
Date: Thu, 1 Nov 2018 20:05:32 +0200 [thread overview]
Message-ID: <a24d481d-1391-d149-3b31-56613f13236f@yahoo.com> (raw)
In-Reply-To: <87zhuslmdg.fsf@gmail.com>
On 11/1/18 7:48 PM, Robert Pluim wrote:
> vordoo <vordoo@yahoo.com> writes:
>> On 11/1/18 6:14 PM, Robert Pluim wrote:
>>> It doesnʼt crash for me. Can you get a backtrace from gdb of the
>>> crash? Thanks Robert
>> Emacs 26.1.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.1) of
>> 2018-11-01: Thread 1 "emacs" received signal SIGSEGV, Segmentation
>> fault. face_at_buffer_position (w=0x11b5c30
>> <bss_sbrk_buffer+8018448>, pos=1,
>> endptr=endptr@entry=0x7fffffff8800, limit=<optimized out>,
>> mouse=mouse@entry=false, base_face_id=<optimized out>) at
>> xfaces.c:5964 5964 memcpy (attrs, default_face->lface, sizeof
>> attrs);
> Thanks for that. Another data point: visiting the org file using
> find-file does not cause this crash, but visiting it via dired does.
> Robert
Yep & I did state that in the original bug report:
"With C-x C-f the file opens OK, and after that it will re-open OK from
the Dired buffer too." :-)
next prev parent reply other threads:[~2018-11-01 18:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 21:29 bug#33222: Crash when visiting an org file from within Dired vordoo
2018-11-01 4:05 ` Eli Zaretskii
2018-11-01 8:41 ` vordoo
2018-11-01 16:14 ` Robert Pluim
2018-11-01 17:31 ` Robert Pluim
2018-11-01 18:43 ` Eli Zaretskii
2018-11-01 17:32 ` vordoo
2018-11-01 17:48 ` Robert Pluim
2018-11-01 18:05 ` vordoo [this message]
2018-11-01 18:12 ` Robert Pluim
2018-11-01 18:46 ` Eli Zaretskii
2018-11-02 10:11 ` Eli Zaretskii
2018-11-02 11:05 ` vordoo
2018-11-02 13:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a24d481d-1391-d149-3b31-56613f13236f@yahoo.com \
--to=vordoo@yahoo.com \
--cc=33222@debbugs.gnu.org \
--cc=rpluim@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.