Re: frames / stacks / source? was Re: coverage/profiling

2007-01-27 Thread Neil Jerram
Kevin Ryde [EMAIL PROTECTED] writes: Neil Jerram [EMAIL PROTECTED] writes: (define coverage-trap (make entry-trap #:behaviour cover-entry)) You don't have to use goops to get a trap do you? In terms of the low-level call outs from the evaluator, no. In terms of the infrastructure that

Re: frames / stacks / source? was Re: coverage/profiling

2007-01-17 Thread Kevin Ryde
Han-Wen Nienhuys [EMAIL PROTECTED] writes: This might also be a good idea to apply to 1.8. Yes, it's a bit obscure otherwise. ___ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel

Re: frames / stacks / source? was Re: coverage/profiling

2007-01-11 Thread Ludovic Courtès
Hi, Han-Wen Nienhuys [EMAIL PROTECTED] writes: Unfortunately, this is way too slow. ** [EMAIL PROTECTED] lilypond]$ time lilypond input/example-1 GNU LilyPond 2.11.10 Hangup real0m2.534s user0m2.456s sys 0m0.063s [EMAIL PROTECTED] lilypond]$ time lilypond -dcoverage

Re: frames / stacks / source? was Re: coverage/profiling

2007-01-10 Thread Ludovic Courtès
Hi, Han-Wen Nienhuys [EMAIL PROTECTED] writes: [EMAIL PROTECTED] info]$ guile guile (trap-enable 'enter-frame-handler) throw from within critical section. Abortado Same here with HEAD and 1.8.0. Here's what happens: #0 0x0fc13f6c in raise () from /lib/tls/libc.so.6 #1 0x0fc15a0c in

Re: frames / stacks / source? was Re: coverage/profiling

2007-01-10 Thread Han-Wen Nienhuys
Ludovic Courtès escreveu: Hi, Han-Wen Nienhuys [EMAIL PROTECTED] writes: [EMAIL PROTECTED] info]$ guile guile (trap-enable 'enter-frame-handler) throw from within critical section. Abortado Same here with HEAD and 1.8.0. Here's what happens: #0 0x0fc13f6c in raise () from

Re: frames / stacks / source? was Re: coverage/profiling

2007-01-10 Thread Han-Wen Nienhuys
Neil Jerram escreveu: Do you think you need to do this in C? (You might do, for reasonable performance - I genuinely don't know yet.) The evaluator already has hooks (see Evaluator trap options in the manual) that allow you to call out to arbitrary Scheme code at the entry and exit of every

Re: frames / stacks / source? was Re: coverage/profiling

2007-01-10 Thread Han-Wen Nienhuys
Neil Jerram escreveu: Han-Wen Nienhuys [EMAIL PROTECTED] writes: Since noone responded, I decided to take a look myself. My overall idea was to do the following: - at the top of deval(), find out current source file and line OK, but with the code where you have it at the moment, you'll

Re: frames / stacks / source? was Re: coverage/profiling

2007-01-09 Thread Ludovic Courtès
Hi, Han-Wen Nienhuys [EMAIL PROTECTED] writes: Han-Wen Nienhuys escreveu: I'd like to run a coverage check on the lilypond source. How do I do this in GUILE? Since noone responded, I decided to take a look myself. [...] +int scm_do_profiling; Are you interested in just profiling or

Re: frames / stacks / source? was Re: coverage/profiling

2007-01-09 Thread Andy Wingo
Hi, On Tue, 2007-01-09 at 10:10 +0100, Ludovic Courtès wrote: For Scheme-level profiling, you may want to use the `statprof' module currently available in guile-lib. It's very easy to set up and provides results similar to `gprof' (it's a statistical profiler, too). For Scheme-level

frames / stacks / source? was Re: coverage/profiling

2007-01-08 Thread Han-Wen Nienhuys
Han-Wen Nienhuys escreveu: I'd like to run a coverage check on the lilypond source. How do I do this in GUILE? Since noone responded, I decided to take a look myself. My overall idea was to do the following: - at the top of deval(), find out current source file and line - invoke some