From: Eli Zaretskii <eliz@gnu.org>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: 21146@debbugs.gnu.org
Subject: bug#21146: 25.0.50; Crash Emacs when S-TAB'ing in Org file
Date: Tue, 28 Jul 2015 13:24:50 +0300 [thread overview]
Message-ID: <83oaiwy3yl.fsf@gnu.org> (raw)
In-Reply-To: <86twsohes4.fsf@example.com>
> From: Sebastien Vauban <sva-news@mygooglest.com>
> Date: Tue, 28 Jul 2015 10:23:07 +0200
>
> When S-TAB'ing in some Org files, I get a crash of Emacs 25.
Isn't that the same as bug #20179?
> I tried to get a backtrace but did not get far:
Small wonder:
> /cygdrive/d/Users/sva/.gdbinit:19: Error in sourced command file:
> No symbol table is loaded. Use the "file" command.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>[...]
> Reading symbols from /cygdrive/c/Program Files (x86)/emacs-trunk/bin/emacs.exe...(no debugging symbols found)...done.
^^^^^^^^^^^^^^^^^^^^^^^^^^
There are no symbols in this binary, so you cannot usefully debug it.
> warning: `/cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll': Shared library architecture i386:x86-64 is not compatible with target architecture i386.
In addition, you are using a 64-bit Cygwin build of GDB:
> This GDB was configured as "x86_64-pc-cygwin".
to debug a 32-bit native Windows build of Emacs, and encounter
incompatibilities due to that.
> I'm not sure what to understand from the 4 warnings with Windows DLL.
>
> And I don't understand those "cannot access memory". Any idea out there?
I hope you understand those now.
> "Hopefully", the problem seems reproducible. Apparently, I can
> systematically crash Emacs with at least one of my Org files.
A reproducible recipe, starting from "emacs -Q", together with an Org
file to use, will be greatly appreciated.
next prev parent reply other threads:[~2015-07-28 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 8:23 bug#21146: 25.0.50; Crash Emacs when S-TAB'ing in Org file Sebastien Vauban
2015-07-28 10:24 ` Eli Zaretskii [this message]
2016-12-07 21:00 ` Glenn Morris
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=83oaiwy3yl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21146@debbugs.gnu.org \
--cc=sva-news@mygooglest.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 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).