Re: debug and backtrace

2009-09-17 Thread Ludovic Courtès
Hi, Neil Jerram writes: > Actually I think I just found and fixed one problem. From the time when > a # was a SMOB, really_make_boot_program in vm.c was still > using SCM_SET_SMOB_FLAGS to set the SCM_F_PROGRAM_IS_BOOT flag - which > meant that it was setting flag 1<<32 :-) which obviously was

Re: debug and backtrace

2009-09-16 Thread Neil Jerram
Andy Wingo writes: > Hi Mike, > > On Sun 13 Sep 2009 16:30, l...@gnu.org (Ludovic Courtès) writes: > >> Mike Gran writes: >> >>> With the default behavior of 1.9.x, REPL debug and backtrace are broken. >> >> Indeed, it looks like the VM frames are ignored. > > Hopefully by the next release, and

Re: debug and backtrace

2009-09-16 Thread Andy Wingo
Hi Mike, On Sun 13 Sep 2009 16:30, l...@gnu.org (Ludovic Courtès) writes: > Mike Gran writes: > >> With the default behavior of 1.9.x, REPL debug and backtrace are broken. > > Indeed, it looks like the VM frames are ignored. Hopefully by the next release, and certainly by the following one, thi

Re: debug and backtrace

2009-09-13 Thread Neil Jerram
l...@gnu.org (Ludovic Courtès) writes: > Hello! > > Mike Gran writes: > >> With the default behavior of 1.9.x, REPL debug and backtrace are broken. > > Indeed, it looks like the VM frames are ignored. I've just hit this too. So here's another example, just in case it's useful. Given a file tes

Re: debug and backtrace

2009-09-13 Thread Ludovic Courtès
Hello! Mike Gran writes: > With the default behavior of 1.9.x, REPL debug and backtrace are broken. Indeed, it looks like the VM frames are ignored. Another example: --8<---cut here---start->8--- scheme@(guile-user)> (letrec ((f (lambda (x) (g x))) (g (lamb