Volkan YAZICI <[EMAIL PROTECTED]> writes:
> On Jul 31 10:53, dave wrote:
>> I had to work through this a while back, and the problem I had was that
>> there are two types of error handler callback - one is called before the
>> stack is unwound, the other after. If you only set the error callback
>
On Jul 31 10:53, dave wrote:
> I had to work through this a while back, and the problem I had was that
> there are two types of error handler callback - one is called before the
> stack is unwound, the other after. If you only set the error callback
> for after the unwind there is no stack to do th
On Mon, 2006-07-31 at 10:13 +0300, Volkan YAZICI wrote:
> On Jul 29 03:08, Clinton Ebadi wrote:
> > You should be able to put something like:
> >
> > SCM_DEVAL_P = 1;
> > SCM_RECORD_POSITIONS_P = 1;
> > SCM_BACKTRACE_P = 1;
> > SCM_RESET_DEBUG_MODE;
> >
> > Into your real_main (th
On Jul 29 03:08, Clinton Ebadi wrote:
> You should be able to put something like:
>
> SCM_DEVAL_P = 1;
> SCM_RECORD_POSITIONS_P = 1;
> SCM_BACKTRACE_P = 1;
> SCM_RESET_DEBUG_MODE;
>
> Into your real_main (the one passed to scm_boot_guile). This will give
> you debug output
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> Hi,
>
> I'm trying to enable debbuging - that's (debug-enable 'backtrace) in
> Scheme - from a C program on-the-fly. Therefore, as far as I
> understand from the quite poorly documented guile manual, I should
> use scm_debug_options() for this purpose. B
Hi,
I'm trying to enable debbuging - that's (debug-enable 'backtrace) in
Scheme - from a C program on-the-fly. Therefore, as far as I
understand from the quite poorly documented guile manual, I should
use scm_debug_options() for this purpose. But I couldn't find any clue
about using this function
