I will ponder how to do that, it will take at least several weeks; I'll
file it through the normal guile bug report system. -- linas
On Mon, Aug 5, 2019 at 1:07 PM Mark H Weaver wrote:
> Hi Linas,
>
> Linas Vepstas writes:
> > However -- if one does call `scm_error` fairly rapidly, from multipl
Hi Linas,
Linas Vepstas writes:
> However -- if one does call `scm_error` fairly rapidly, from multiple
> threads, one will eventually hit a race condition and get a crash.
If you could produce a small, self-contained example demonstrating this,
it would enable us to investigate further.
How utterly embarrassing. Please ignore most of this verbose and difficult
email chain. Yes, guile-2.9.2 is still crashing, but almost all of my
analysis was wrong. Turns out that my scheme code was calling `(10)` i.e.
taking an integer, and treating it as a function, and attempting to call
it. So
Oh, I get it. I think the bug is this: VM_DEFINE_OP (7,
return_values,...)
finds some mcode, and calls it. What it found was the emit_get_callee_vcode
but it is totally pointless to call this mcode, since we're returning, and
not
calling. So its just not useful.
Worse, it gets called with garba
Seem to be narrowing it down ... or at least, I have more details ...
On Wed, Jul 17, 2019 at 4:44 PM Linas Vepstas
wrote:
>
>
> On Wed, Jul 17, 2019 at 12:49 PM Mark H Weaver wrote:
>
>> Hi Linas,
>>
>> > Investigating the crash with good-old printf's in libguile/vm.c produces
>> > a vast ocea
On Wed, Jul 17, 2019 at 12:49 PM Mark H Weaver wrote:
> Hi Linas,
>
> > Investigating the crash with good-old printf's in libguile/vm.c produces
> > a vast ocean of prints ... that should have not been printed, and/or
> should
> > have been actual errors, but somehow were not handled by scm_error
Hi Linas,
> Investigating the crash with good-old printf's in libguile/vm.c produces
> a vast ocean of prints ... that should have not been printed, and/or should
> have been actual errors, but somehow were not handled by scm_error.
> Using today's git pull of master, here's the diff containing a
Investigating the crash with good-old printf's in libguile/vm.c produces
a vast ocean of prints ... that should have not been printed, and/or should
have been actual errors, but somehow were not handled by scm_error.
Using today's git pull of master, here's the diff containing a printf:
--- a/libg
Exactly the same crash, same stack trace (slightly different line numbers),
with a fresh pull today:
commit 89e28df1c9069dcb65188fe7b3973c333d87d7e2
Author: Andy Wingo
Date: Thu Jun 20 14:02:05 2019 +0200
which is the current HEAD on master.
FWIW, 60-odd guile threads waiting here:
Below was for
guile (GNU Guile) 2.9.2.14-1fb399
--linas
On Sun, Jul 14, 2019 at 4:59 PM Linas Vepstas
wrote:
>
> So, here's my next installment on using guile-2.9.2. The first installment
> said that I'd piled up CPU-months of guile 2.9.2 experience without any
> crashes. Well, now, a different
So, here's my next installment on using guile-2.9.2. The first installment
said that I'd piled up CPU-months of guile 2.9.2 experience without any
crashes. Well, now, a different workload crashes in minutes. Below is a
highly simplified, edited gdb session -- it crashes because it unexpectedly
abo
Hi Mark,
Sorry for the late reply; my email client mananged to hide your email where
I won't see it. I need to fix this.
On Thu, Jun 6, 2019 at 11:28 PM Mark H Weaver wrote:
>
> You'll need to look at the stack frames on the Scheme stack. It can be
> done from GDB if necessary, but it might be
Mark H Weaver writes:
>> Two are stuck here:
>>
>> #0 __lll_lock_wait () at
>> ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
>> #1 0x7f343ca69bb5 in __GI___pthread_mutex_lock (
>> mutex=mutex@entry=0x7f343d4f0f40 )
>> at ../nptl/pthread_mutex_lock.c:80
>> #2 0x7f343d213
Hi Linas,
Linas Vepstas writes:
> I'm trying to understand how scm_jit_enter_mcode leads to
> scm_timed_lock_mutex ...
This simply means that 'lock-mutex' was called from Scheme, and
specifically from Scheme code that has been compiled to machine code by
our JIT compiler.
> I want to know who
14 matches
Mail list logo
