IRC channel logs

2020-06-16.log

back to list of logs

<tinga>Is there a way to show the source location of the current continuation?
<tinga>From the debugger, I mean.
<tinga>Ah, ",frame 0" it seems
***terpri__ is now known as terpri
<apteryx>dsmith-work: yes, edebug is awesome
<apteryx>Realgud supports many compiler and supposedly makes it easy to hook new ones. Could be interesting to try to add support for debugging Guile in Realgud.
<jackhill>daviid: ah, cool :) I thought you might upon seeing 3.0 removed from GUILE_PKG
***wxie1 is now known as wxie
<tohoyn>sneek, botsnack
<sneek>:)
***apteryx is now known as Guest37148
***apteryx_ is now known as apteryx
<wingo>moin
<dsmith-work>Hey Hi Howdy, Guilers
<civodul>wingo: i see a build failure for master on i686-linux: https://paste.debian.net/1152366/
<civodul>does that ring a bell?
<civodul>hmm it could be that my prebuilt directory had stale .go files
<dsmith-work>civodul: I had no probs building for 32bit intel
<dsmith-work>civodul: From a fresh clone
***tazjin is now known as JSFzKHVpbnQ4PTEx
***JSFzKHVpbnQ4PTEx is now known as tazjin
<dadinn>lastlog
<heisenberg-25>I am using the guile static profile and it works. But in the output it displays some procedure names as "anon #xb12c48". anyone had similar issue or know why?
<manumanumanu>heisenberg-25: are the anon procedures lambdas?
<heisenberg-25>manumanumanu: do you mean anonymous procedures? I am not sure. but there isn't a function named anon in my code.
<dsmith-work>heisenberg-25: What version? There was a recent commit: df22eb5 Statprof reports primitive names
<heisenberg-25>dsmith-work: I am using guile-3.0.2
<dsmith-work>Ok. That commit is after 3.0.2
***janneke_ is now known as janneke
<heisenberg-25>dsmith-work: re-building guile from the source
<manumanumanu>heisenberg-25: i mean, are you passing any (lambda (x y z) ...) to a higher order function? Iirc those procedures are called something like that in the profiler
<justin_smith>also, many macros will end up creating lambda blocks internally
<heisenberg-25>manumanumanu: yes.
<heisenberg-25>dsmith-work: the commit you suggested fixes the issue, :)
<dsmith-work>Yey!
<heisenberg-25>wingo: is there a way to suspend the run-fibers call if an exception occurs. Right now it prints the exception stacktracae but hangs. and while running from the guile repl, I have to do Ctrl + Z to terminate guile (because Ctlr + C) doesn't work
<rekado>found this on Guile’s Elisp: https://emacsninja.com/posts/state-of-emacs-lisp-on-guile.html
<rekado>looks like there are a few misunderstandings
<rekado>ugh, don’t look at the hackenews “discussion” of this…
<civodul>rekado: the author may be doing something wrong, but it looks like they made some effort to get the thing running
<civodul>of course, they probably started with a misconception and have a confirmation bias
<justin_smith>I think the main misconception is that guile's elisp would be usable without the c functions in emacs
<civodul>right, like buffer functions