From: Pieter van Oostrum <pieter-l@vanoostrum.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 39962@debbugs.gnu.org, Pieter van Oostrum <pieter@vanoostrum.org>
Subject: bug#39962: 27.0.90; Crash in Emacs 27.0.90
Date: Sun, 08 Mar 2020 10:34:20 +0100 [thread overview]
Message-ID: <lxh7yz6vhf.fsf@cochabamba.vanoostrum.org> (raw)
In-Reply-To: <329e58b1-6255-311e-bdd8-b6f5b3d5208f@cs.ucla.edu> (Paul Eggert's message of "Sat, 7 Mar 2020 23:42:51 -0800")
Paul Eggert <eggert@cs.ucla.edu> writes:
>> In GNU Emacs 27.0.90 (build 1, i686-apple-darwin10.0.0, NS
>> appkit-1561.61 Version 10.13.6 (Build 17G11023))
>
> "i686"? Are you building a 32-bit executable? If so, does the problem go
> away if you build the more-typical 64-bit executable?
Sorry, I got that i686 stuff from a compile script I picked up somewhere. I'll try to recompile without that.
But, Emacs is still a 64-bit executable:
The file command gives:
Emacs: Mach-O 64-bit x86_64 executable, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL|PIE>
> What compiler and version are you using? And what GDB version are you
> using?
gcc -v
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
gdb version 9.1_0 with python3.7
>
>> (gdb) p args[0]
>> $25 = XIL(0x3960)
>> (gdb) xtype
>> Lisp_Symbol
>> (gdb) xsymbol
>> $26 = (struct Lisp_Symbol *) 0x3af8
>> Cannot access memory at address 0x3b00
>
> Something's wrong here. xsymbol should have output something like:
>
> $8 = (struct Lisp_Symbol *) 0x10515f0 <lispsym+14688>
>
> Try this instead (my examples show output on my Ubuntu 18.04 x86-64 platform):
>
> (gdb) p args[0]
> $25 = XIL(0x3960)
> (gdb) xgetsym $25
> (gdb) p $ptr
> $27 = (struct Lisp_Symbol *) 0x10515f0 <lispsym+14688>
>
> I assume yours will output something like "$27 = (struct Lisp_Symbol *)
> 0x3af8" instead. If so, try this:
>
> (gdb) xgetptr $25
> (gdb) p/x $ptr
> $28 = 0x3960
>
> Assuming you get that, try this:
>
> (gdb) p ((struct Lisp_Symbol *) ((char *)lispsym + 0x3960))
> $29 = (struct Lisp_Symbol *) 0x10515f0 <lispsym+14688>
>
> I assume yours will output something like "$29 = (struct Lisp_Symbol *)
> 0x3af8" instead. If so, please try this:
>
> (gdb) p (char *)lispsym
> $30 = 0x104dc90 <lispsym> "\230\001"
> (gdb) p (char *)&lispsym[0]
> $31 = 0x104dc90 <lispsym> "\230\001"
>
> My *guess* is that the above two lines will differ due either to a bug
> in your compiler or in your debugger. Your $30 will equal 408. If I'm
> right, the attached patch should work around your compiler/debugger bug.
> Of course this will merely help you debug Emacs; it won't fix the
> original bug you reported. So if this fixes your problem please redo the
> backtrace info Eli asked for.
>
Here is that output.
(gdb) xgetsym $25
(gdb) p $ptr
$31 = (struct Lisp_Symbol *) 0x3af8
(gdb) xgetptr $25
(gdb) p/x $ptr
$32 = 0x3960
(gdb) p ((struct Lisp_Symbol *) ((char *)lispsym + 0x3960))
$33 = (struct Lisp_Symbol *) 0x3af8
(gdb) p (char *)lispsym
$34 = 0x198 <error: Cannot access memory at address 0x198>
(gdb) p (char *)&lispsym[0]
'lispsym' has unknown type; cast it to its declared type
(gdb)
So I guess your patch might not help. Or is it worthwhile to try anyway?
But anyway, to use that patch, I have to create a new instance of the crash.
And then, I also will recompile first.
--
Pieter van Oostrum
www: http://pieter.vanoostrum.org/
PGP key: [8DAE142BE17999C4]
next prev parent reply other threads:[~2020-03-08 9:34 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 23:55 bug#39962: 27.0.90; Crash in Emacs 27.0.90 Pieter van Oostrum
2020-03-07 7:48 ` Eli Zaretskii
2020-03-07 8:40 ` Pieter van Oostrum
2020-03-07 8:41 ` Pieter van Oostrum
2020-03-07 10:51 ` Eli Zaretskii
2020-03-07 11:06 ` Pieter van Oostrum
2020-03-07 13:10 ` Eli Zaretskii
2020-03-07 15:06 ` Pieter van Oostrum
2020-03-07 15:17 ` Eli Zaretskii
2020-03-07 15:49 ` Pieter van Oostrum
2020-03-07 16:07 ` Eli Zaretskii
2020-03-07 17:21 ` Pieter van Oostrum
2020-03-07 18:01 ` Eli Zaretskii
2020-03-07 19:14 ` Pieter van Oostrum
2020-03-07 19:21 ` Eli Zaretskii
2020-03-07 22:07 ` Pieter van Oostrum
2020-03-09 4:00 ` Pip Cet
2020-03-08 7:42 ` Paul Eggert
2020-03-08 9:34 ` Pieter van Oostrum [this message]
2020-03-08 10:05 ` Paul Eggert
2020-03-08 21:37 ` Pieter van Oostrum
2020-03-08 21:58 ` Pieter van Oostrum
2020-03-08 22:34 ` Paul Eggert
2020-03-08 23:58 ` Pieter van Oostrum
2020-03-09 0:01 ` Paul Eggert
2020-03-09 13:26 ` Pieter van Oostrum
2020-03-09 17:10 ` Eli Zaretskii
2020-03-09 19:48 ` Pieter van Oostrum
2020-03-10 13:37 ` Pieter van Oostrum
2020-03-09 19:51 ` Paul Eggert
2020-03-09 21:32 ` Pieter van Oostrum
2020-03-10 10:52 ` Pieter van Oostrum
2020-03-10 14:19 ` Pip Cet
2020-03-10 16:36 ` Pieter van Oostrum
2020-03-11 14:32 ` Pip Cet
2020-03-11 15:16 ` Pieter van Oostrum
2020-03-11 15:43 ` Pip Cet
2020-03-11 15:51 ` Paul Eggert
2020-03-11 16:21 ` Eli Zaretskii
2020-03-11 17:52 ` Eli Zaretskii
2020-03-11 18:53 ` Pip Cet
2020-03-11 19:34 ` Eli Zaretskii
2020-03-12 10:32 ` Pip Cet
2020-03-12 15:23 ` Eli Zaretskii
2020-03-12 20:36 ` Pip Cet
2020-03-13 9:39 ` Eli Zaretskii
2020-03-13 13:56 ` Pip Cet
2020-03-13 16:30 ` Eli Zaretskii
2020-03-14 9:02 ` Pip Cet
2020-03-14 15:39 ` Pip Cet
2020-03-14 16:00 ` Paul Eggert
2020-03-14 16:15 ` Pip Cet
2020-03-14 16:57 ` Eli Zaretskii
2020-03-14 18:34 ` Pip Cet
2020-03-14 19:09 ` Paul Eggert
2020-03-14 20:10 ` Eli Zaretskii
2020-03-15 12:12 ` Pip Cet
2020-03-15 14:53 ` Eli Zaretskii
2020-03-15 12:09 ` Pip Cet
2020-03-15 14:50 ` Eli Zaretskii
2020-03-16 16:31 ` Stefan Monnier
2020-03-11 20:03 ` Pieter van Oostrum
2020-03-12 13:55 ` Pip Cet
2020-03-12 18:13 ` Pieter van Oostrum
2020-03-12 20:00 ` Pip Cet
2020-03-13 8:09 ` Eli Zaretskii
2020-03-13 8:39 ` Pip Cet
2020-03-13 9:19 ` Eli Zaretskii
2020-03-13 17:43 ` Pieter van Oostrum
2020-03-14 3:38 ` Richard Stallman
2020-03-14 8:37 ` Eli Zaretskii
2020-03-14 9:16 ` Pip Cet
2020-03-14 15:34 ` Pip Cet
2020-03-13 17:42 ` Pieter van Oostrum
2020-03-13 19:34 ` Eli Zaretskii
2020-03-13 21:35 ` Pieter van Oostrum
2020-03-14 8:08 ` Eli Zaretskii
2020-03-14 21:32 ` Pieter van Oostrum
2020-03-15 19:49 ` Pieter van Oostrum
2020-03-15 19:57 ` Eli Zaretskii
2020-03-15 23:26 ` Pieter van Oostrum
2020-03-16 10:44 ` Pieter van Oostrum
2020-03-16 15:07 ` Eli Zaretskii
2020-03-16 15:33 ` Pip Cet
2020-03-16 17:19 ` Pip Cet
2020-03-17 3:29 ` Pieter van Oostrum
2020-03-17 4:54 ` Pip Cet
2020-03-17 5:20 ` Pip Cet
2020-03-17 8:45 ` Pieter van Oostrum
2020-03-17 13:54 ` Pip Cet
2020-03-17 15:27 ` Pieter van Oostrum
2020-03-17 20:16 ` Pip Cet
2020-03-17 23:32 ` Pieter van Oostrum
2020-03-18 15:05 ` Eli Zaretskii
2020-03-19 13:23 ` Pieter van Oostrum
2020-03-19 13:57 ` Pip Cet
2020-03-21 21:22 ` Pieter van Oostrum
2020-03-22 14:21 ` Eli Zaretskii
2020-03-22 15:48 ` Pip Cet
2020-03-23 19:34 ` Pip Cet
2020-03-17 8:40 ` Pieter van Oostrum
2020-03-17 15:33 ` Eli Zaretskii
2020-03-17 20:59 ` Paul Eggert
2020-03-18 6:17 ` Pip Cet
2020-03-18 9:22 ` Robert Pluim
2020-03-18 11:38 ` Pieter van Oostrum
2020-03-18 11:57 ` Paul Eggert
2020-03-18 14:08 ` Pip Cet
2020-03-19 19:17 ` Pieter van Oostrum
2020-03-19 19:31 ` Pip Cet
2020-03-19 21:30 ` Pieter van Oostrum
2020-03-18 14:08 ` Eli Zaretskii
2020-03-16 18:36 ` Pieter van Oostrum
2020-03-13 7:58 ` Eli Zaretskii
2020-03-10 15:10 ` Eli Zaretskii
2020-03-10 18:23 ` Pieter van Oostrum
2020-03-11 8:22 ` Paul Eggert
2022-04-30 12:38 ` Lars Ingebrigtsen
2022-05-29 13:19 ` Lars Ingebrigtsen
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=lxh7yz6vhf.fsf@cochabamba.vanoostrum.org \
--to=pieter-l@vanoostrum.org \
--cc=39962@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=pieter@vanoostrum.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 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.