freenode/#sicl - IRC Chatlog
Search
13:54:52
beach
Am I reading the SLIME debugger chapter right? I don't see a way of setting a breakpoint at some point in a function, neither before a program is started for execution, nor when it has failed and the user is staring at a backtrace.
13:56:01
beach
All I see is the set of three stepping functions available only when things have failed and we have a backtrace.
13:57:06
beach
What is the "next form in the current function" and what does it mean to step "to" it?
13:58:12
beach
sldb-step seems clear, but it mentions only CMUCL. But it doesn't say what happens when one of those breakpoints is reached.
14:01:24
beach
In case it is not clear what I am doing, I am compiling a list of shortcomings with our current development environment, and in particular with the "nice debugger" that we have.
14:02:10
beach
I also want to make it clear that I am convinced that the people who wrote the SLIME debugger are not to blame here. I am sure they did a fine job with what they had to work with and with the resources available.
14:02:28
Bike
my impression is that stepping pretty much doesn't work at all in sbcl, and given how common sbcl is, you know
14:02:35
beach
Well, it depends on the implementation, and I am guessing most implementations have very limited support.
14:03:32
beach
Now, let's turn to examining stack frames. And this aspect is likely implementation-specific as well.
14:04:23
beach
Some of them may have names such as VAR-1 where I actually used a variable named VAR.
14:06:15
scymtym
(defun (x) (let ((x …)) …)) results in multiple variables named X which get disambiguated as X, X#1, etc. to show the "shadowed" values
14:07:40
beach
That was my guess, yes. I think it would be better to show them as source positions of definition (in the sense of DEF-USE etc).
15:59:41
beach
ck_: I started a list of tasks. See metamodular.com/SICL/sicl-specification.pdf chapter 30.
16:00:16
beach
I am open to additions and modifications to this list. And I'll answer any questions anyone might have, of course.
16:04:45
Bike
i mean, i can code a fix myself, i just thought you might want to look at my plan first
16:06:15
beach
Today, I spent all day with the next chapter of Dyomkin's book. It's a lot of work, and I fear that it is not going to be enough.