From: Eli Zaretskii <eliz@gnu.org>
To: Gemini Lasswell <gazally@runbox.com>
Cc: 33014@debbugs.gnu.org
Subject: bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function
Date: Fri, 12 Oct 2018 11:12:17 +0300 [thread overview]
Message-ID: <83murjwplq.fsf@gnu.org> (raw)
In-Reply-To: <87d0sh9hje.fsf@runbox.com> (message from Gemini Lasswell on Wed, 10 Oct 2018 22:30:29 -0700)
> From: Gemini Lasswell <gazally@runbox.com>
> Date: Wed, 10 Oct 2018 22:30:29 -0700
>
> When I run some byte-compiled code which creates some threads, and then,
> while a thread is blocked, interactively evaluate the function which
> was used to create that thread, Emacs has a fatal error or segmentation
> fault when the thread becomes unblocked.
Can you please make a smaller stand-alone test case, which doesn't
require patching Emacs? That will make it much easier to try
reproducing the problem.
> Thread 7 (Thread 0x7f1cd4dec700 (LWP 21837)):
> #0 terminate_due_to_signal (sig=sig@entry=6,
> backtrace_limit=backtrace_limit@entry=2147483647) at emacs.c:369
> #1 0x00000000005a4d99 in die (msg=msg@entry=0x678d52 "HASH_TABLE_P (a)",
> file=file@entry=0x6768a5 "lisp.h", line=line@entry=2241) at alloc.c:7094
> #2 0x00000000006122b5 in XHASH_TABLE (a=...) at lisp.h:2241
> #3 exec_byte_code (bytestr=..., vector=..., maxdepth=..., args_template=...,
> nargs=nargs@entry=0, args=<optimized out>,
> args@entry=0x16eac38 <bss_sbrk_buffer+9926040>) at bytecode.c:1403
> #4 0x00000000005cb972 in funcall_lambda (fun=..., nargs=nargs@entry=0,
> arg_vector=0x16eac38 <bss_sbrk_buffer+9926040>,
> arg_vector@entry=0x158ec58 <bss_sbrk_buffer+8500664>) at eval.c:3057
> #5 0x00000000005c818b in Ffuncall (nargs=nargs@entry=1,
> args=args@entry=0x158ec50 <bss_sbrk_buffer+8500656>) at eval.c:2870
> #6 0x000000000064443b in invoke_thread_function () at thread.c:684
> #7 0x00000000005c728f in internal_condition_case (
> bfun=bfun@entry=0x644400 <invoke_thread_function>, handlers=...,
> handlers@entry=XIL(0xc3c0), hfun=hfun@entry=0x644320 <record_thread_error>)
> at eval.c:1373
> #8 0x0000000000644dd1 in run_thread (state=0x158ec30 <bss_sbrk_buffer+8500624>)
Can you show the Lisp backtrace of this thread? Also, what is the
offending object 'a' in this frame:
> #2 0x00000000006122b5 in XHASH_TABLE (a=...) at lisp.h:2241
and what was its parent object in the calling frame?
Thanks.
next prev parent reply other threads:[~2018-10-12 8:12 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 [this message]
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
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
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=83murjwplq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33014@debbugs.gnu.org \
--cc=gazally@runbox.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).