Search
Sunday, 25th of September 2022, 23:43:37 UTC
0:13:18
drmeister
https://www.irccloud.com/pastebin/2FgWixPj/
0:13:43
drmeister
You will see that it does a lot of scanning before it causes the error.
0:14:45
drmeister
Change this... (MERGE-PATHNAMES #P"../" (UIOP/OS:GETCWD))
0:14:50
drmeister
to (uiop/os:getcwd)
0:16:15
drmeister
What's interesting is that it dies after processing a lot of directories.
0:16:47
drmeister
I'm also running clasp/main alongside it doesn't die.
0:17:25
drmeister
Hang on - I'll have them scan the same root directory.
0:27:41
drmeister
There's a problem with the vm.
0:28:14
drmeister
https://www.irccloud.com/pastebin/wAp7AaL3/
0:29:40
drmeister
I'm loading this...
0:29:42
drmeister
(trace asdf/source-registry::process-source-registry-cache)
0:29:42
drmeister
(trace UIOP/STREAM:SAFE-READ-FILE-FORM
0:29:42
drmeister
UIOP/STREAM:read-file-form
0:29:42
drmeister
UIOP/STREAM:CALL-WITH-INPUT-FILE
0:29:42
drmeister
UIOP/STREAM:SLURP-STREAM-FORM
0:29:43
drmeister
core:universal-error-handler
0:29:45
drmeister
(setf *default-pathname-defaults* #P"/home/meister/Development/clasp/")
0:29:46
drmeister
(ASDF/SOURCE-REGISTRY:INITIALIZE-SOURCE-REGISTRY
0:29:46
drmeister
(LIST :SOURCE-REGISTRY (LIST :TREE #P"/home/meister/Development/clasp/")
0:29:47
drmeister
:INHERIT-CONFIGURATION))
0:30:00
drmeister
And I get that vm error.
2:32:59
Bike
random evening thought: compiling discriminators in a dedicated thread might be easier for making it work as well as for performance reasons
2:33:05
Bike
have to get it working to begin with first, tho
2:50:33
drmeister
We are blowing through the top of the stack.
2:53:55
Bike
hmm. the sjlj unwind ought to make sure the destination dynenv is on the stack before it does anything
3:02:44
drmeister
I mean - the stack pointer is exceeding the top of the stack.
3:14:19
Bike
like the bytecode stack pointer?
3:17:49
drmeister
https://usercontent.irccloud-cdn.com/file/7SAfcNZH/image.png
3:35:50
drmeister
nargs words (arguments) are pushed onto the stack and then bytecode_call returns with those words popped off the stack - correct?
3:39:45
drmeister
Uh return values.
3:43:27
drmeister
Bike: Is there a simple relationship between the vm._stackPointer on entry to bytecode_call and on normal return?
9:12:27
Guest1362
** NICK 040AAGS3Q
11:18:28
attila_lendvai_
** NICK attila_lendvai
11:38:45
drmeister
There is a lot of stuff being left on the stack...
11:38:48
drmeister
https://www.irccloud.com/pastebin/f8bDL55m/
11:39:31
drmeister
This is when ASDF is performing `ASDF/SOURCE-REGISTRY:INITIALIZE-SOURCE-REGISTRY`
11:39:58
drmeister
It works by trying to open files and if they don't exist it signals an error and the stack is supposed to unwind.
11:40:12
drmeister
But the vm._stackPointer isn't being updated.
11:41:08
drmeister
I added a guard to the vm stack so if we attempt to write into it then it segfaults.
11:41:42
drmeister
This is to the end of the stack - now it won't overwrite other structures and give confusing errors.
11:42:22
drmeister
The dump above is a dump of consecutive words on the stack
11:42:46
drmeister
::notify Bike Can you check the logs this morning.
11:42:46
Colleen
drmeister: Got it. I'll let Bike know as soon as possible.
Monday, 26th of September 2022, 11:43:37 UTC