freenode/#clasp - IRC Chatlog
Search
3:18:01
drmeister
::notify selwyn Turning on logging of jit events in gdb: set debug jit 1 turns it on.
3:18:24
drmeister
No - sorry - I was working on building gdb and figuring out how it initializes itself.
3:19:20
drmeister
The shit c language means they have to scrape all of the c code to gather up all of the _initialize_xxx functions and write them into a file that is constructed by the build system.
3:20:20
drmeister
Seriously, nobody seems to be able to write a C or C++ program that doesn't involve some kind of scraper.
6:08:06
drmeister
::notify Bike I found the problem - it's not Instance_sp instance((gc::Tagged)tinstance) . It's Instance_sp instance(gc::Tagged)tinstance.raw_()); We shouldn't allow casting of a T_sp to a gc::Tagged and I have no idea right now why that casts to 0x1 (bleh) but that's what it was doing.
7:18:26
Colleen
selwyn: drmeister said 4 hours ago: Turning on logging of jit events in gdb: set debug jit 1 turns it on.
11:29:50
drmeister
selwyn: Buuuuut I can't get it to work. gdb seems completely unresponsive to jit events.
11:41:34
drmeister
::notify Bike I'm getting a bad dtree gfvm program once it starts loading fli.lsp - I'll paste some info in a bit. I added a lot more logging to the dtree interpreter.
12:09:12
Colleen
Bike: drmeister said 6 hours, 1 minute ago: I found the problem - it's not Instance_sp instance((gc::Tagged)tinstance) . It's Instance_sp instance(gc::Tagged)tinstance.raw_()); We shouldn't allow casting of a T_sp to a gc::Tagged and I have no idea right now why that casts to 0x1 (bleh) but that's what it was doing.
12:09:12
Colleen
Bike: drmeister said 27 minutes, 38 seconds ago: I'm getting a bad dtree gfvm program once it starts loading fli.lsp - I'll paste some info in a bit. I added a lot more logging to the dtree interpreter.
12:13:41
drmeister
I added more logging information. Where you generate the program try putting in some validation to catch where bad opcodes are entering.
12:14:06
drmeister
We can run with this high level of logging - it doesn't slow the build down by much.
12:16:08
Bike
which is because in the opcode map *isa* in dtree.lsp, i have eql-search instaed of eql.
14:51:23
Bike
"Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS" well this is going to suck
15:01:46
drmeister
I have memory profiling in place - you can generate flame graphs for allocations.
15:02:37
drmeister
It's not as bullet proof as regular flame graphs - it may need a bit of tweaking to get it to work properly.