From: Eli Zaretskii <eliz@gnu.org>
To: Gemini Lasswell <gazally@runbox.com>
Cc: 33014@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function
Date: Tue, 16 Oct 2018 22:25:21 +0300 [thread overview]
Message-ID: <83in21snha.fsf@gnu.org> (raw)
In-Reply-To: <878t2xd90z.fsf@runbox.com> (message from Gemini Lasswell on Tue, 16 Oct 2018 11:46:36 -0700)
> From: Gemini Lasswell <gazally@runbox.com>
> Cc: Andreas Schwab <schwab@linux-m68k.org>, 33014@debbugs.gnu.org
> Date: Tue, 16 Oct 2018 11:46:36 -0700
>
> My knowledge of what gcc does and how the code it generates works is
> superficial, but I don't see why an optimizer would find it necessary to
> save the following values:
>
> - The value of 'fun' in Ffuncall after it is used as an argument for
> funcall_lambda.
>
> - The value of 'fun' in funcall_lambda after it is used to calculate
> the arguments to exec_byte_code.
>
> - The value of 'vector' in exec_byte_code after the calculation of
> vectorp.
There are calling frames as well. For GC to pay attention to a Lisp
object, it is enough to have that object _somewhere_ on the stack.
Anyway, are you saying that stack marking doesn't work in optimized
code? We've been using this technique for the last 17 years without
problems; why would the fact that we have more than one thread change
that? The same arguments you submit are valid for a single-threaded
Emacs, right?
I think the chance of something like what you describe to happen here
are small, and we shouldn't throw in the towel so quickly. I don't
think we've exhausted all the other possibilities, not yet.
> gdb shows a value for fun in frame 11, but when I try to print
> XIL(0x7fecdacdc468) it complains about it being an invalid lisp object,
> and then the result of "info frame 11" shows some similar values,
> so I'm thinking gdb is confused:
It's quite possible that GDB is not confused, and you've found some
evidence of the problem.
How did you try to print XIL(0x7fecdacdc468)? Maybe we should take a
good look at this object.
> I haven't figured out how to get gdb to print the Lisp backtrace of one
> thread while execution is stopped in a different one.
You can't, AFAIR. The code that helps us produce a Lisp backtrace
doesn't work in that case.
next prev parent reply other threads:[~2018-10-16 19:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 5:30 bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function Gemini Lasswell
2018-10-12 8:12 ` Eli Zaretskii
2018-10-12 20:02 ` Gemini Lasswell
2018-10-13 6:23 ` Eli Zaretskii
2018-10-13 17:17 ` Gemini Lasswell
2018-10-13 18:04 ` Eli Zaretskii
2018-10-14 19:29 ` Gemini Lasswell
2018-10-15 2:37 ` Eli Zaretskii
2018-10-14 19:46 ` Andreas Schwab
2018-10-15 14:59 ` Eli Zaretskii
2018-10-15 16:22 ` Gemini Lasswell
2018-10-15 16:41 ` Eli Zaretskii
2018-10-16 18:46 ` Gemini Lasswell
2018-10-16 19:25 ` Eli Zaretskii [this message]
2018-10-16 19:38 ` Eli Zaretskii
2018-10-19 0:22 ` Gemini Lasswell
2018-10-19 8:44 ` Eli Zaretskii
2018-10-19 20:05 ` Gemini Lasswell
2018-10-20 6:41 ` Eli Zaretskii
2018-10-20 8:23 ` Andreas Schwab
2018-10-20 10:20 ` Eli Zaretskii
2018-10-20 11:30 ` Andreas Schwab
2018-10-29 18:24 ` Gemini Lasswell
2018-10-29 19:41 ` Eli Zaretskii
2018-10-19 19:32 ` Gemini Lasswell
2018-10-17 16:21 ` Eli Zaretskii
2018-10-18 1:07 ` Gemini Lasswell
2018-10-18 17:04 ` Eli Zaretskii
2018-10-19 0:39 ` Gemini Lasswell
2018-10-19 8:38 ` Eli Zaretskii
2018-10-29 18:56 ` Stefan Monnier
2018-10-31 4:49 ` Paul Eggert
2018-10-31 15:33 ` Eli Zaretskii
2018-11-01 23:15 ` Gemini Lasswell
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=83in21snha.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33014@debbugs.gnu.org \
--cc=gazally@runbox.com \
--cc=schwab@linux-m68k.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.