IRC channel logs
2025-12-10.log
back to list of logs
<cow_2001>i don't know how to debug effectively. all i know is peek. my deficiencies annoy me <rlb>I've done an awful lot of debugging of fairly complex things via the (f)printf equivalent in any given language --- not fancy, but nearly always works (until the problems are IO related themselves :) ). <FuncProgLinux>is there a flymake package for guile? I've been searching for one over the iternet but have been unsuccessful :( it would be nice to have errors show up on Emacs from time to time <cow_2001>FuncProgLinux: oh that would have been great! <dsmith>cow_2001, Been coding for about 40 years, and mostly used print debugging. gdb/debuggers are very effective for segfaults and asm errors. <rlb>In guile I often just use fprintf on the C side and some hacked up format wrapper on the scm side, or just format. Not saying that's all we should have, just noting I do that a lot :) <rlb>agreed --- now and then a backtrace from gdb for a repeatable segfault is also handy <cow_2001>i hear that sly and slime in common lisp have amazing stuff <dsmith>Only time that fails is when the bug gorks up the stack, and gdb gets lost. <cow_2001>trying to figure out how to do that kind of stuff <cow_2001>there's a famous quote about the supremacy of carefully thinking + carefully put print <dsmith>Guile very anoyingly gets an error, and then has another error when printing or writing the backtrack. *verry* annoying <dsmith>cow_2001, Sometime it's good to "poke it with a stick" and see which way it moves. <dsmith>I can't explain exactly what that is. <dsmith>change *something*. Timing. force an error. <mwette>Python's pdb.set_trace() is my fav, but I also love gdb. There is a lot of debugging infrastructure in guile but I think it is not complete. I dug in at one time but gave up fttb. I played with a pdb.set_trace() for guile, but it's not great (ref: https://github.com/mwette/guile-jtd). <listentolist>Is there something like the string-search-backward procedure of mit-scheme in Guile? I want to search backwards for a pattern in a string starting from a specific index. <listentolist>string-contains seems to always start the search from the beginning?