freenode/#clasp - IRC Chatlog
Search
15:53:24
Bike
so although it seems like backtraces are going to be a mess for the forseeable future, we ought to come up with a stable interface for accessing the information.
15:55:15
Bike
so that we don't have to push a new commit to slime every week when some llvm change renders our previous approach futile, that sort of thing
16:24:11
Bike
for each frame we should at least have readers for let's seee... the function, the arguments, local variables, source location
16:24:45
drmeister
And you'd like them to be copied and prepared so that users can access these things without touching pointers.
16:25:29
Bike
yeah. like right now the frame-source-location in slime is basically ext:code-source-position of core:backtrace-frame-return-address. not too hard to pack into a function, so that we only mess with pointers interanlly
16:26:04
Bike
what i'm not sure about is whether to represent frames as actual objects (though we do need objects) or as indices into the stack, but that's what you've been changing with ihs-top and such
16:28:25
drmeister
How about you design a good API and we can create the CLASP-DEBUG package to put the functions within.
16:29:45
Bike
including foreign frames seems fine, though we should maybe retain some options to skip them