lines. The crash happens as you describe if there are at least 9 lines
in history; if there are exactly 8, then pressing up won't crash, but
pressing down afterward will.
Don't know if that helps at all or not.
It did!
The code crashed if you had 8..15, 24..31, 40..48 etc
(when num_entries8
... Not very helpful backtrace though.
On a somewhat related note: It is actually possible to tell gdb about
the pike code.
The API is however somewhat .. interresting, you basically generate an
ELF-file with only debugging sections, in memory, and pass it to GDB:
Can we get a more minimal test case in the testsuite?
Can we get a more minimal test case in the testsuite?
Well, sure, but it seems to be a fairly esoteric crash condition, how
often do we write machine code that uses the wrong register, and that
for whatever reason _almost_ works?
It is not all that likely to be in the same place if it happens
Partially done now.
Still left to fix are the very complex rules (define
variable,global,function, local function), the issue is that a lot of
things are renumbered when the optional_stars token is removed, and
since optional_stars is now so optional that it is never ever set I
have not bothered
