Megatest

Update of "using trace with the megatest executable"
Login
Overview

Artifact ID: 9659dc4664d89f54d54e830b8d403ac2a165cfe9
Page Name:using trace with the megatest executable
Date: 2014-11-26 09:33:51
Original User: matt
Next b6cd6ec04c546827c0ce1ab343858b92b8001e99
Content

Using trace to debug Megatest issues

  1. Create ~/.megatestrc
    (use trace)
    (import trace)
    ;; list the functions you think might illuminate the problem here
    runs:process-expanded-tests
    )
  2. Patch trace to emit a little info on where the function was called
    chicken-install -r trace
    cd trace
    patch -p0 <<EOF
    > *** trace.scm 2014-11-26 09:29:50.000000000 -0700
    > --- ../../trace/trace.scm 2014-11-25 21:12:41.000000000 -0700
    > ***************
    > *** 61,66 ****
    > --- 61,68 ----
    >       (trace-indent)
    >       (set! *trace-indent-level* (fx+ 1 *trace-indent-level*))
    >       (write (cons name args) port)
    > +     (write ", Called from: " port)
    > +     (write (conc (car (reverse (get-call-chain)))))
    >       (write-char #\newline port)
    >       (flush-output port) ) )
    > EOF
    chicken-install
    
  3. Run your megatest runs and dig through the various logs :)