Ole Myren Rohne <[EMAIL PROTECTED]> writes:
> Exception during backtrace does occur in some situations on my Dec 16
> 16:05 build. I think it was there before as well, but I used to blame
> guile-gtk for crashes during backtrace.
I think, then, that we safely can assume that this bug is not caus
Mikael Djurfeldt writes:
> This should, in principle, only affect GC if you have defined
> GUILE_NEW_GC_SCHEME in __scm.h. Did you do that?
No.
> Is it possible for you to tell me exactly the time and date when you
> checked out your Guile?
I did cvs update guile-core on Mar 16 08:15
> s
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 (q
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: (m
The purpose of this report is to show how changing (if #f '() (begin
...)) into (cond (#f '()) (else ...)) makes the backtracing go crazy.
Regards, Ole
guile> (use-modules (ice-9 streams))
guile> (debug-enable 'backtrace)
(stack 2 debug backtrace depth 20 maxdepth 1000 frames 3 inden
