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
