| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 11 Jun 2012 13:11:36 +0200 From: Eric Valette <Eric.Valette@...e.fr> To: Alan Cox <alan@...rguk.ukuu.org.uk> CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Linux 3.2.19 kernel panic does not enter KDB On 06/11/2012 12:54 PM, Alan Cox wrote: > kdb not getting entered is not itself a bug - its a limitation. Ok. I'm still wondering if KDB is not broken on 3.2.19. If on a working system I do echo g > /proc/sysrq-trigger even from a tty all I see is the help and I'm back to the login shell. Actions like echo t > /proc/sysrq-trigger are logged but I cannot really enter the debugger... -- eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists