shoshin has quit [Read error: Connection reset by peer]
shoshin4 is now known as shoshin
aw- has joined #picolisp
aw- has quit [Quit: Leaving.]
Lambdajack has quit [Quit: AFK]
orivej has joined #picolisp
_whitelogger has joined #picolisp
aw- has joined #picolisp
orivej has quit [Ping timeout: 240 seconds]
_whitelogger has joined #picolisp
<tankf33der>
in this 20h run all passed under gc+. kangaroo12 append passed too. rest will be tomorrow.
<Regenaxer>
Good to know
<Regenaxer>
I still have no clue about stress.l
<Regenaxer>
Just know it always happens around binRead and extern
<Regenaxer>
But all related code looks correct to me
<Regenaxer>
It happens in binRead, and is gc-related
<Regenaxer>
stress.l with (gc 80) can't reproduce
<Regenaxer>
I'm stuck
<Regenaxer>
would need to release PilBox, but it is too dangerous if DB is not safe
orivej has joined #picolisp
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #picolisp
pointfree has quit [Ping timeout: 272 seconds]
pointfree has joined #picolisp
pointfree has quit [Excess Flood]
pointfree has joined #picolisp
<tankf33der>
i gonna blow up heap by malloc and try to run under gc+ again. i will increase step by step and run tests in loop. maybe will find something important. run @lib/test.l is good candidate.
<tankf33der>
because it is relatively fast under gc+
<Regenaxer>
Very good
<Regenaxer>
I'm checking the sources
<Regenaxer>
Good thing, I did many changes and clean ups
<Regenaxer>
But nothing critical I think
<tankf33der>
i used already this technics in spring
<Regenaxer>
ok
<Regenaxer>
Let's hope you find something
<Regenaxer>
as I said above, it looks very much that it is gc-related
<Regenaxer>
My tests with (gc 80) are still running
<Regenaxer>
gc-related, but also always waitFd -> binRead -> extern
<Regenaxer>
reading external symbols with plio
<Regenaxer>
It never crashed in other parts of stress.l
orivej has quit [Ping timeout: 256 seconds]
<Regenaxer>
Ha! Now I can reproduce the crash outside of stress.l!!