From: Eli Zaretskii <eliz@gnu.org>
To: David Reitter <david.reitter@gmail.com>
Cc: 9671@debbugs.gnu.org
Subject: bug#9671: 24.0.50; Two bidi crashes
Date: Thu, 06 Oct 2011 01:45:28 -0400 [thread overview]
Message-ID: <E1RBgls-0003qu-Ku@fencepost.gnu.org> (raw)
In-Reply-To: <77D6525D-E49A-4E04-848D-045D6650A33C@gmail.com> (message from David Reitter on Wed, 5 Oct 2011 16:49:47 -0400)
> From: David Reitter <david.reitter@gmail.com>
> Date: Wed, 5 Oct 2011 16:49:47 -0400
> Cc: 9671@debbugs.gnu.org
>
> First of all, this may have to do with GDB and passing Emacs environment variables to another Emacs instance.
But the original reports did not say Emacs was started from GDB that
itself was started from another Emacs instance. Did I miss something?
> This may explain why we're seeing this abort in bidi:
>
> I am reproducing at least some type of crash in bidi_initialize() when I debug Emacs (24) from gdb session inside an Emacs 23 - this occurs all the time, but not when I start it outside of Emacs/GDB:
I know about this issue, but I thought it only happens on MS-Windows,
because the Windows build pushes values of EMACSDATA and EMACSLOADPATH
into its own environment, and those values correspond to the version
of Emacs that runs. Does Emacs on Apple systems also do that?
Anyway, use the GDB command "unset environment" to remove these
variables from the environment of Emacs being debugged. Do that
_before_ you type the "run" command in GDB.
> The abort in question happens here:
>
> bidi_mirror_table = uniprop_table (intern ("mirroring"));
> if (NILP (bidi_mirror_table))
> abort ();
>
> uniprop_table returns Qnil in this situation (chartab.c:1340):
Yes, because Emacs 23 didn't have the "mirroring" table in
uni-mirrored.el.
> EMACSDATA=/Users/dr/ae.git/nextstep/Aquamacs.app/Contents/Resources/etc
> EMACSPATH=/Users/dr/ae.git/nextstep/Aquamacs.app/Contents/MacOS/bin
> EMACS=t
> EMACSLOADPATH=/Users/dr/ae.git/nextstep/Aquamacs.app/Contents/Resources/lisp:/Users/dr/ae.git/nextstep/Aquamacs.app/Contents/Resources/leim
> INSIDE_EMACS=23.3.50.39,comint
> EMACSDOC=/Users/dr/ae.git/nextstep/Aquamacs.app/Contents/Resources/etc
>
> Does this explain what's going on?
It does, but how is this related to the original report? There was no
GDB there nor another instance of Emacs, at least they were not
mentioned. That's why I said I can only understand the original
report if Emacs was badly deployed.
And the other crash was entirely unrelated to this issue anyway.
next prev parent reply other threads:[~2011-10-06 5:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 21:01 bug#9671: 24.0.50; Two bidi crashes David Reitter
2011-10-04 21:15 ` Eli Zaretskii
[not found] ` <9726D990-8E8E-4013-99F1-E479848B8246@gmail.com>
[not found] ` <83mxdgqvrr.fsf@gnu.org>
2011-10-05 20:49 ` David Reitter
2011-10-06 5:45 ` Eli Zaretskii [this message]
2011-10-06 10:40 ` David Reitter
2011-10-06 11:27 ` Eli Zaretskii
2011-10-06 15:32 ` David Reitter
2011-10-06 17:55 ` Eli Zaretskii
2011-10-06 17:59 ` David Reitter
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=E1RBgls-0003qu-Ku@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=9671@debbugs.gnu.org \
--cc=david.reitter@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 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).