freenode/#clasp - IRC Chatlog
Search
13:19:27
yitzi
beach: I am looking to add indenter support to common-lisp-jupyter. I was going to use my own indenter https://github.com/yitzchak/cl-indentify
13:20:28
yitzi
It probably needs some work since it doesn't have a real parser and just relies on sort of a stylesheet protocol. drmeister said you had some experience/throughts?
13:23:29
beach
I see. Well, then I am afraid I have nothing to add. I tried that in (first) Climacs, and the result was as bad as what Emacs is doing. So for Second Climacs we are doing it completely differently.
13:25:02
beach
We know how to parse the buffer, and I know how to indent various forms, but I have yet to come up with an architecture for the indentation code so as to avoid duplication.
13:26:13
beach
So, since that is essentially READ, the result is very close to what the compiler would do.
13:28:43
beach
So how do you deal with edits? Like if someone inserts a character in the middle, do you scan everything from the beginning?
13:30:11
yitzi
Yeah, it wasn't really designed for an editor nor was it designed for usage by others. Wrote it on a whim. It seems pretty good for my usage, but I'd like to explore the eclector route since I just put some code completion and inspection into common-lisp-jupyter that uses eclector
13:31:11
beach
Well, I'll try to remember to keep you up to date when I come up with an architecture for indentation.
13:31:34
yitzi
jupyter has a complete_request message that I was going to indentation when the user tries to do completion on a paren
14:11:34
Bike
i think i'll just clean up the internal numbers interface a little before i get started on anything significant, it's a serious mess
14:52:18
Bike
alright well actually i see a ton of stuff in cando using Bignums (i.e. whatever mpz class) directly
18:08:41
jcob
heyy just checked clasp today and I noticed that the type interference code got merged. Woohoo!
19:10:57
kpoeck
does a build with latest master work for you? I get datum: TYPE-ERROR (:DATUM 73767624523776 :EXPECTED-TYPE LIST) when iclasp-boehm tries to compile asdf (even after distclean)
19:15:04
kpoeck
79: gctools::initializeBoehm(int (*)(int, char**, bool&, int&, int&), int, char**, bool, int, int)
19:32:21
kpoeck
with lldb I see I backtrace: https://gist.github.com/kpoeck/27d10efdbaaa4c49dbe9a8e052a4253f
20:41:32
drmeister
I got an evaluation copy of the Undo debugger - it's a time-traveling debugger that lets you rewind the cpu instruction by instruction.
20:46:27
drmeister
I start by continuing forward to the core:gdb call and then forward to the cl__error
20:49:39
drmeister
I'm thinking while I'm typing here. How do I leverage this to debug a problem in our MPS version?
21:02:03
kpoeck
karlosz wscript.config is in https://gist.github.com/kpoeck/70bdd9848ba5204ab2ffb1825d17c8dd
21:03:51
karlosz
your error sounds vaguely familiar and i can't remember whether it was a config thing or a stale stuff thing
21:06:02
karlosz
kpoeck: could you try making your debug options look more like this: https://paste.gnome.org/p8bfqx4mf
21:08:40
drmeister
kpoeck: If you want to get a more descriptive backtrace you can do the following. Copy and paste the backtrace you got into a file - say /tmp/backtrace.txt
21:09:32
drmeister
Then clasp/src/profiler/symbolicate.lisp -i /tmp/backtrace.txt -o /tmp/backtrace-w-symbols.txt -s /tmp/perf-<pid>.map
21:10:15
drmeister
kpoeck: Yes. Any file that contains strings that look like ... 0x000000011a611708
21:10:56
drmeister
symbolicate.lisp recognizes those and if they fall in the function address ranges that are in /tmp/perf-<pid>.map - it converts those addresses into jitted symbol names.
21:13:03
drmeister
You need the perf-<pid>.map file that corresponds to the same run that generated the backtrace.
21:13:22
drmeister
kpoeck: It's hard to tell from the error and backtrace that you pasted - but at what stage of the build does that error happen?
21:27:40
drmeister
You also have guards on. Both of these might catch bad problems that I might be missing with my wscript.config
21:54:23
SAL9000
drmeister: have you heard of anything similar to the Undo debugger you mentioned, which has Windows support?
21:54:36
SAL9000
(i.e. Undo itself doesn't have Windows support, but do you know another one that does?)