orivej has quit [Ping timeout: 256 seconds]
mmmattyx has quit [Quit: Connection closed for inactivity]
emacsomancer has quit [Ping timeout: 260 seconds]
emacsomancer has joined #picolisp
aw- has quit [Quit: Leaving.]
aw- has joined #picolisp
aw- has quit [Quit: Leaving.]
aw- has joined #picolisp
_whitelogger has joined #picolisp
rob_w has joined #picolisp
orivej has joined #picolisp
mtsd has joined #picolisp
beneroth has quit [Quit: Leaving]
<
tankf33der>
Regenaxer: now i belive gc+ has data race or deadlocks or something like this.
<
Regenaxer>
Hi tankf33der
<
Regenaxer>
It hangs?
<
tankf33der>
some file should finished in ~6h and i killed it after 19h. before it finished successfully.
<
tankf33der>
looks like
<
Regenaxer>
Full CPU load?
<
tankf33der>
i think thats why math.l hanged too.
<
tankf33der>
i killed it after 25h.
<
Regenaxer>
Would be interesting to know what caused this
<
Regenaxer>
Can you start it again with some tracing?
<
Regenaxer>
ie start it with pil -"trace 'test" ... +
<
Regenaxer>
We should know after 6 h then where it hangs
<
tankf33der>
in general: every function of big code base is ok, but in whole run it could hang somewhere sometimes.
<
tankf33der>
worst scenario.
<
tankf33der>
for example these two runs sit here for 4h.
<
tankf33der>
good i know what function it is, i will count dots.
<
Regenaxer>
one dot per function?
<
tankf33der>
lets wait till evening.
aw- has quit [Quit: Leaving.]
<
Regenaxer>
No hurry
<
Regenaxer>
Ah, btw, I fixed 'diff' and 'sect' this morning
mtsd has quit [Quit: mtsd]
<
tankf33der>
if two run will not print a dot in 2h i will count it as hanged.
orivej has quit [Ping timeout: 240 seconds]
_whitelogger has joined #picolisp
mtsd has joined #picolisp
ppdx has joined #picolisp
ppdx has quit [Remote host closed the connection]
orivej has joined #picolisp
orivej has quit [Ping timeout: 240 seconds]
orivej_ has joined #picolisp
orivej_ has quit [Ping timeout: 256 seconds]
orivej has joined #picolisp
Nistur has joined #picolisp
orivej has quit [Ping timeout: 246 seconds]
orivej_ has joined #picolisp
mtsd has quit [Quit: Leaving]
<
tankf33der>
i calculated run time under gc+
<
tankf33der>
so i have to wait.
rob_w has quit [Quit: Leaving]
<
tankf33der>
diff and sect checked. passed.
<
tankf33der>
============
<
tankf33der>
found this is wrong under gc+
orivej_ has quit [Ping timeout: 256 seconds]
<
tankf33der>
Regenaxer: also i could run gc+ check for pil63 too if you show me how to enable it.
<
Regenaxer>
I see, 'fish' again ...
<
Regenaxer>
ok, I'd need to investigate how I did it back then
<
Regenaxer>
Seems I have a version from 15jul17
<
Regenaxer>
Must diff to see how much changed meanwhile
<
Regenaxer>
The first part can be ignored
<
Regenaxer>
The relevant part starts at 501c483
<
Regenaxer>
Not sure if useful
<
tankf33der>
so i need only ld part. i see
<
Regenaxer>
yes, (Avail) cleared
<
tankf33der>
trying
<
Regenaxer>
If it smokes, just pull the plug ;)
<
Regenaxer>
I look closer at 'fish'
<
Regenaxer>
Or could it be 'filter'?
<
tankf33der>
this is fish. proved.
<
tankf33der>
i postpone pil64 gc+ run, without full correct patch or file this is impossible modify gc.l correctly. torture.
<
Regenaxer>
It is just one identical change in those lines
<
Regenaxer>
But right, perhaps better not to waste time on that
<
tankf33der>
who will do if i dont.
<
Regenaxer>
I think I know the fault in 'fish'
<
Regenaxer>
released
<
Regenaxer>
'V' was not saved
<
Regenaxer>
It was saved, but overwritten during recursion, so that parts of it were not safe when the second recursion branch started
<
Regenaxer>
Hmm, wait
<
Regenaxer>
Not correct now
<
Regenaxer>
uninitialized cell on the stack now
<
Regenaxer>
Ah, no! No problem :)
<
tankf33der>
fish checked, ok now.
orivej has joined #picolisp
<
Regenaxer>
Cool! Thanks!
<
tankf33der>
i am running gc+ tests under pil64.
<
tankf33der>
minimal bundle passed. enough.
<
Regenaxer>
Perfect
mmmattyx has joined #picolisp