IRC channel logs

2017-01-07.log

back to list of logs

<wak-work>anyone know where the code to embed source paths in .go files lives?
<linas>wingo some of what I said earlier today was wrong. just fyi
<artyom-poptsov1>Hello Guilers! Guile-ICS 0.1.0 is out, if someone interested: https://lists.gnu.org/archive/html/guile-user/2017-01/msg00008.html
<artyom-poptsov1>Oh, there's a problem with building Guile-ICS 0.1.0 (tests are failing.) I'll release a new version with a bugfix soon.
<sneek>Understood.
<artyom-poptsov1>Hey sneek, I'm glad you're interested in Guile-ICS too. ;-)
<janneke>(gdb) b _start
<janneke>Segmentation fault
<janneke>
<janneke>wow
<daviid>fi, guile-gnome-platform 2.16.4 is now in debian testing
<wingo>good evening
<paroneayea>hi wingo
<linas>hi wingo I've got it -- theres some kind of thread leakage in both guile-2.0 and 2.2 and I have a very simple demo of it -- am opening bug report
<linas> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25386
<linas>so who, here, besides wingo, knows guile threads?
<linas>the above bug report has a super-simple demo that leaks threads like crazy, and then crashes.
<linas>I'm guessing that its actually leaking some continuation or something, even though the thread has exited.
<linas>I'd like help finding that...
<linas>how might I print everything in the current dynamic state?