00:39 <chzyhndz> okay

00:39 <chzyhndz> I'm trying out a few of the examples

00:39 <chzyhndz> and getting the occasional segmentation fault

00:51 <theodus> chzyhndz: That shouldn't happen. Which examples and what OS are you using?

00:53 <chzyhndz> I'm using Arch on a 32 bit atom, and the echo example is probably the simplest one with the problem; I've had it with mailbox without args and with httpget

00:53 <chzyhndz> echo seems to work fine, until I connect to the port, at which point it segfaults

00:56 <chzyhndz> also, I kinda just cloned the ponyc git repo, and compiled it,

00:56 <chzyhndz> or just did 'make' 'sudo make install'

00:57 <theodus_> What version of LLVM did you use?

01:00 <theodus_> You can check by running llvm-config --version

01:01 <chzyhndz> 3.9.0

01:04 <chzyhndz> hmm, let me just update everything

01:04 <chzyhndz> and see if that fixes the problem

01:32 <SeanTAllen> 3.9.1 is the supported version now

01:36 <SeanTAllen> actually 3.9.0 is still the officially support version. I just opened a PR to move us to 3.9.1

01:37 <SeanTAllen> chzyhndz: i suspect the 32 bit is the issue. Most folks are on 64 bit platforms so 32 bit would be more likely to have bugs (plus our CI is all 64 bits) so 32 bits is "best effort" support.

01:38 <SeanTAllen> chzyhndz: if you can build a debug version of the compiler and app and open a issue with the backtrace you get from lldb after a crash, that would be awesome. If you don't know how to do that, let me know and I can assist.

01:45 <chzyhndz> alright

01:48 <chzyhndz> I'll try to do that.

01:49 <chzyhndz> I'm guessing its just a matter of downloading clang+llvm, compiling it with debugging enabled, then doing the same with ponyc, right?

01:59 <SeanTAllen> you dont need to do that with clang+llvm

01:59 <SeanTAllen> when you build ponyc do

01:59 <SeanTAllen> make install config=debug

01:59 <SeanTAllen> it defaults to

01:59 <SeanTAllen> make install config=release

01:59 <SeanTAllen> then when buiding the app do ponyc -d

02:00 <SeanTAllen> do you know how to get a backtrack from lldb?

02:00 <SeanTAllen> or how to run an application in lldb?

02:03 <chzyhndz> lldb <app>, right?

02:20 <SeanTAllen> ya

02:28 <chzyhndz> hmm, is it alright if I come back tommorrow with this? it's gotten rather late where I am, I'm afraid.

02:30 <chzyhndz> Still, thanks for helping me out though!

02:55 <SeanTAllen> if you can open an issue on the github repo chzyhndz that would be best

15:35 <TwoNotes> An actor _final() gets called when the actor is disposed. FileStream is an actor that owns an 'iso' File. Yet FileStream lacks its own dispose or _final method. So how do I close the underlying File?

15:42 <Praetonus> TwoNotes: An object's _final() method is always called when the object is collected, and an actor collects every object that it owns before being collected. So the File field will be closed when the FileStream is collected

15:43 <Praetonus> But having a dispose method on FileStream to prematurely close the file definitely seems useful to me

15:49 <TwoNotes> I just want to make sure it gets flushed cleanly. It is for a log file.

15:49 <TwoNotes> My top level Main actor has a SignalHandler, and a dispose method, but there is nothing to call!

15:50 <TwoNotes> And I can't close the File myself, becasue it was passed off as an 'iso' to the FileStream

15:54 <Praetonus> If your program exits cleanly, the file will get flushed eventually. You just can't control when

15:54 <Praetonus> Oh, didn't see the part about SignalHandler

15:55 <Praetonus> Do you close the program yourself after handling that signal?

16:24 <SeanTAllen> TwoNotes: you want to inform the rest of your application to stop sending data to the file stream, and start shutting down the remaining parts of the application, the filestream wont shut down until its processed all its messages and when it does, it will shut down if there are no other actors to send it messages

16:43 <TwoNotes> Praetonus, that was the idea. It is a server that does not exit by itself - it has to be killed. But I want to make sure the log buffers are flushed.

16:44 <TwoNotes> If I close all TCP sessions, that will prevent new stuff being written to the log, but it would not necessarily flush the buffer

16:45 <TwoNotes> I observed that just killing it with ^C did NOT flush the buffers - the last htings written to the log were sometimes not on disk. That is why I am adding the SignalHandler

16:52 <TwoNotes> I guess I do want to stop listening for incoming connections, and close all existing ones. Then the program should exit all by itself when all external stimulus goes away, correct? There are no timers.

16:57 <SeanTAllen> TwoNotes: yes

18:40 <Praetonus> I've written an introduction to Pony (in French), in case anyone is interested. It is available here: https://zestedesavoir.com/articles/1329/decouverte-du-langage-pony/

23:00 <carado> hi ! is there any kind of benchmark for the pony gc ? should i worry about the length of GC pauses if i aim to make a video game ?