Ole Myren Rohne <[EMAIL PROTECTED]> writes:
> While investigating my streams, throw and backtrace problem, I came
> across the following peculiarity - still on today's cvs version
>
> Regards, Ole
>
> guile> (if #f '() (throw 'test 0))
> ERROR: In procedure throw in expression (throw (quote test) 0):
> ERROR: unhandled-exception: test 0
> ABORT: (misc-error)
>
> Type "(backtrace)" to get more information.
> guile> (backtrace)
>
> Backtrace:
> 0* #f
> 1 [throw . #<freed cell 0x402cfa08; GC missed a reference>]
Thanks for your bug-report.
There has recently been three large changes to Guile:
1. The removal of a call to SCM_ASYNC_TICK from SCM_ALLOW_INTS.
This could be the reason why you no longer get `Exception during
displaying of backtrace: signal'. This problem can probably be solved
by calling SCM_ASYNC_TICK from suitable place within the backtrace
printing routines. (We have to discuss this problem, though. I'll
bring it up on the list later.)
2. The introduction of 2-word cells
This influences the GC.
3. The introduction of a new GC scheme.
This should, in principle, only affect GC if you have defined
GUILE_NEW_GC_SCHEME in __scm.h. Did you do that?
Is it possible for you to tell me exactly the time and date when you
checked out your Guile?
Probably, though, this problem isn't caused by any of these changes,
but by some earlier change, since you say that you have observed the
"Exception during backtrace" for some time. Do you know for how long?
Best regards,
/mdj
