After the new code generation I get a consistent crash if I start hilfe and does arrow up. Not very helpful backtrace though.
Pike v8.0 release 3 running Hilfe v3.5 (Incremental Pike Frontend)
Program received signal SIGSEGV, Segmentation fault. 0x00002aaaacd583d8 in ?? () (gdb) bt #0 0x00002aaaacd583d8 in ?? () #1 0x0000000000000027 in ?? () #2 0x00000000008902e0 in ?? () #3 0x00002aaaacd986b1 in ?? () #4 0x00002aaaac12d1b0 in ?? () #5 0x0000000000886338 in ?? () #6 0x00000000008902e0 in ?? () #7 0x000000000095c080 in ?? () #8 0x000000000041e060 in eval_instruction ( pc=0x2aaaacd986b1 "UH\211\345AWAVAUATSH\203\354\bI\211\377M\213w H\215\005\365\377\377\377I\211F(M\213/I\213N8H\213\001H\213I\bI\211E") at /home/nilsson/pike/src/interpret.c:1707 #9 catching_eval_instruction ( pc=0x2aaaacd986b1 "UH\211\345AWAVAUATSH\203\354\bI\211\377M\213w H\215\005\365\377\377\377I\211F(M\213/I\213N8H\213\001H\213I\bI\211E") at /home/nilsson/pike/src/interpret.c:2749 #10 0x000000000041f3b0 in inter_return_opcode_F_CATCH ( addr=0x2aaaac2b4000 "@\323\022\254\252*") at /home/nilsson/pike/src/interpret.c:1291 #11 0x00002aaaacd98699 in ?? () #12 0x0000000000034cf0 in ?? () #13 0x00000000008902e0 in ?? () #14 0x0000000000000000 in ?? ()
... 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:
https://sourceware.org/gdb/current/onlinedocs/gdb/JIT-Interface.html
pike-devel@lists.lysator.liu.se