[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's
From: |
Eli Zaretskii |
Subject: |
bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function |
Date: |
Thu, 18 Oct 2018 20:04:03 +0300 |
> From: Gemini Lasswell <gazally@runbox.com>
> Cc: 33014@debbugs.gnu.org, schwab@linux-m68k.org
> Date: Wed, 17 Oct 2018 18:07:39 -0700
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > After thinking about this a bit, I don't really agree with the last
> > one: the compiler could indeed stop tracking 'vector', but not
> > XVECTOR (vector)->contents, and we are interested in the latter.
>
> If the compiler stops tracking 'vector', and the garbage collector frees
> it, doesn't that cause XVECTOR (vector)->contents to be overwritten?
Hmmm... could be.
> > However, I'm still not convinced we are there. Can we establish which
> > element(s) of the bytecode vector are GC'ed in this scenario?
>
> I'll see if I can figure that out.
>
> Is there an easy way to print the function binding of a Lisp symbol from
> gdb?
Not sure what you mean by "the function binding" in this context.
I hope something like the following will do:
(gdb) p fun
(gdb) xpr
Let me know if this isn't what you meant.
Thanks.
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, (continued)
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Gemini Lasswell, 2018/10/19
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Eli Zaretskii, 2018/10/20
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Andreas Schwab, 2018/10/20
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Eli Zaretskii, 2018/10/20
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Andreas Schwab, 2018/10/20
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Gemini Lasswell, 2018/10/29
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Eli Zaretskii, 2018/10/29
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Gemini Lasswell, 2018/10/19
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Eli Zaretskii, 2018/10/17
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Gemini Lasswell, 2018/10/17
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function,
Eli Zaretskii <=
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Gemini Lasswell, 2018/10/18
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Eli Zaretskii, 2018/10/19
- bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Stefan Monnier, 2018/10/29
bug#33014: 26.1.50; 27.0.50; Fatal error after re-evaluating a thread's function, Paul Eggert, 2018/10/31