Nikodemus Siivola <nikodemus@...> writes:
>> The work on making backtraces look prettier has caused the side-effect
>> of SB-DEBUG:ARG not working as one might expect. (sb-debug:arg 0) on
>> a XEP frame gets the number of arguments, even if the fact that the
>> frame is a XEP is hidden from the user.
> Ouch. My bad. I had not thought of this at all.
> Would having (ARG N) work depending the current value of
> *SHOW-ENTRY-POINT-DETAILS* be ok, or would that be too magical?
I think ARG and similar should be consistent with what the user sees.
So, yes, if *..-DETAILS* is nil then ARG should fetch from the
synthetic frame (or however you want to describe it), I think.
Incidentally, today in the amusement regarding immediate single-floats
I wished quite strongly for a "disassemble current function" command.
(Not that it would have pinpointed the problem, which turned out to be
GC, but it might have told us where the problem wasn't.)