id summary reporter owner description type status priority milestone component version resolution keywords cc blockedby blocking platform 2598 sshd occasionally segfaults on connect (possibly when forking) anevilyak bonefish "Once in a while when connecting via ssh, the sshd segfaults. However, neither gdb nor debug_server seem to be able to make heads or tails of it, gdb displays several hundred stack entries all of which are ?? followed by {{{ Previous frame inner to this frame (corrupt stack?) }}} Whereas debug_server lists the following in syslog: {{{ KERN: vm_soft_fault: va 0xb000 not covered by area in address space KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xb7d6, ip 0xb7d6, write 0, user 1, thread 0xe3 KERN: vm_page_fault: thread ""sshd"" (227) in team ""sshd"" (227) tried to read address 0xb7d6, ip 0xb7d6 (""???"" +0xb7d6) KERN: debug_server: TeamDebugHandler::Init(): Failed to get executable path of team 227: No such file or directory KERN: debug_server: Thread 227 entered the debugger: Segment violation KERN: stack trace, current PC 0xb7d6 : KERN: (0x7ffeea84) 0x7ffeeaa0 (sshd_main_stack + 0xfffaa0) KERN: (0x7ffeed4c) 0x20e4f1 (sshd_seg0ro + 0xe4f1) KERN: (0x7ffeee2c) 0x20fbe2 (sshd_seg0ro + 0xfbe2) KERN: (0x7ffeef7c) 0x20c9af (sshd_seg0ro + 0xc9af) KERN: (0x7ffeefac) 0x1008ea (runtime_loader_seg0ro + 0x8ea) }}} " bug closed normal R1 System/Kernel R1/pre-alpha1 fixed All