How do i get line number information for Chicken scheme errors

Question

I am trying to isolate the cause of an error. The interpreter give "bad argument type" and a call history of 16 identical lines: <eval> [procedure name] (sexpr). However, this procedure is call from many different places in the program. Is there a way to find out which one of these locations is the source of the problem without going thru the time consuming process of putting print calls in front of each and every possible candidate?

Not sure there are many Chicken users here. Did you try on their mailing list? it's quite active. — uselpa, Jul 06 '13 at 07:12

ramrunner · Accepted Answer · 2013-07-06T20:49:56.707

1

you can use the debug egg and change your procedure to first call trace. Otherwise you could try and compile it with

csc --debug 2 <foo.scm>

edited Jul 06 '13 at 20:49

answered Jul 06 '13 at 17:44

ramrunner

1,362
10
20

Interesting, is there a corresponding option for `csi`? – xuinkrbin. Jul 06 '13 at 18:37
none that i know of, but calling debug/trace is essentially the same. – ramrunner Jul 06 '13 at 18:39
Thanks, I guess calling that with `&& ./foo` is just as good. – xuinkrbin. Jul 06 '13 at 20:42

How do i get line number information for Chicken scheme errors

1 Answers1