Re: problem becouse scm_tc7_contin is not defined

[Marius Vollmer]

P Pareit <address@hidden> writes:

> > SCM
> > scm_internal_cwdr_no_unwind (scm_catch_body_t body, void *body_data,
> >                          scm_catch_handler_t handler, void *handler_data,
> >                          SCM_STACKITEM *stack_start)
> > {
> >   return scm_internal_cwdr (body, body_data, handler, handler_data,
> >                         stack_start);
> > }
> >
> > That version is not very interesting but it will ket us see whether
> > the bug is with scm_internal_cwdr_no_unwind or with some other part of
> > Scwm or Guile.
> >
> 
> Well, it gave me absolutly the same bactrace as before:

Aha!  So it is not the fault of scm_internal_cwdr_no_unwind.  Since
you already have the bug in the debugger, please try to figure out
what is happenening exactly.

> (gdb) backtrace
> #0  0x4007bd5c in scm_hook_empty_p (hook=0x0) at hooks.c:227

This looks wrong.  scm_hook_empty_p should probably not be called with
a NULL argument.

> #6  0x400942a4 in scm_internal_cwdr (body=0x80604e0 <scwm_body_eval_str>,
>     body_data=0x8092120, handler=0x805686c <scm_handle_by_message_noexit>, 
>     handler_data=0x809023a, stack_start=0x0) at root.c:283

Note that stack_start is NULL...

> #7  0x0806ef4f in scm_internal_cwdr_no_unwind (
>     body=0x80604e0 <scwm_body_eval_str>, body_data=0x8092120,
>     handler=0x805686c <scm_handle_by_message_noexit>, handler_data=0x809023a,
>     stack_start=0xbffff464) at guile-compat.c:64

while it isn't here.  Maybe GDB doesn't see the whole truth.  Try
compiling without "-O2".

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405