Hi,

I have a strange backtrace with Pike 7.6.25 that I didn't see before:

#0 0x080e3e22 in gc_mark_object_as_referenced (o=0x99a00b3) at object.c:1721 1721 DOUBLEUNLINK(first_object, o); (gdb) bt #0 0x080e3e22 in gc_mark_object_as_referenced (o=0x99a00b3) at object.c:1721 #1 0x08111263 in run_queue (q=0x823d2e8) at queue.c:43 #2 0x080b42ac in do_gc (ignored=0x82cc4f8, explicit_call=0) at gc.c:2844 #3 0x0809e34b in low_call_callback (lst=0x823d254, arg=0x0) at callback.c:167 #4 0x08074f38 in low_mega_apply (type=APPLY_LOW, args=1, arg1=0x8415b3c, arg2=0x3) at apply_low.h:215 #5 0x08072f35 in jump_opcode_F_CALL_OTHER (arg1=1) at interpret_functions.h:1941 #6 0x0844b6ea in ?? () #7 0x00000001 in ?? () #8 0x00000001 in ?? () #9 0x0842caa0 in ?? () #10 0x0842caa8 in ?? () #11 0x40c3268c in ?? () #12 0x40c32614 in ?? () #13 0x08136d0f in append_path_unix (s=0x0, path= {ptr = 0x842caa8 "\004\211\025(\002", shift = 1086531212}, len=138594976) at combine_path.h:263 #14 0x080761d4 in o_catch ( pc=0x844b569 "¡0Ò#\b\203@\034\024\213H$\213\035 Ò#\b\213Q\004\211S\004\213\t\211\vf\203ù\aw\002ÿ\002\203Ã\b\211\035 Ò#\bèµKÂÿ\205À\017\205Ñ") at interpret.c:2050 #15 0x0807062c in jump_opcode_F_CATCH () at interpret_functions.h:1236 #16 0x0844b563 in ?? () #17 0x00000003 in ?? () #18 0x0891a708 in ?? () #19 0x00000003 in ?? () #20 0x40c32864 in ?? () #21 0x00000008 in ?? () #22 0x00000000 in ?? () #23 0x099c6cb8 in ?? () #24 0x40c327b0 in ?? () #25 0x40cf7000 in ?? () #26 0x40c327f0 in ?? () #27 0x080761d4 in o_catch ( pc=0x880dc8f "¡(Ò#\b\213\r Ò#\b\211\b\203À\004£(Ò#\b\213\0350Ò#\b\017¿S>\203Â\033\211T$\b\213S8\211T$\004\211\f$èÌQ\215ÿ¡ Ò#\b\203À\b£ Ò#\bÇ\004$") at interpret.c:2050 Previous frame identical to this frame (corrupt stack?)

I don't know what produced it and how to reproduce it:(

Ideas?

/ David