Re: PLEASE: debugging embedded guile code

[Neil Jerram <neil@ossau.uklinux.net>]

>>>>> "Bruce" == Bruce Korb <bkorb@veritas.com> writes:

    Bruce> Neil Jerram wrote:
    >> Now you've really lost me, I'm afraid.  Why don't you use a catch,
    >> either in Scheme or in C, to catch the error?

    Bruce> Yes, I can catch it.  Now what do I print out?  I know the
    Bruce> file and line where the scheme text started, but I don't
    Bruce> know what Guile's objections are and I don't know how far
    Bruce> into the text the problem text was.

OK.  (I don't see what this has to do with atexit, but never mind
that.)  The current situation is that:

- Guile's objection is encoded:

  - primarily in the throw key (a symbol) that is the first arg passed
    to the catch handler, e.g. 'misc-error

  - secondarily in the remaining throw args, in a way which is
    key-dependent and very poorly documented

- the location where the problem arose is not supplied by default, but
  can be found out by capturing the current stack - (make-stack #t) -
  in a lazy-catch handler.

My impression from various emails is that there may be issues with
this model, so my purpose here is to explore whether there are issues
and, if so, to address them.

So, given this description, can you be more precise about which (if
any) parts of it are causing you trouble?

Thanks,
        Neil



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel