From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756921AbcBBTkx (ORCPT ); Tue, 2 Feb 2016 14:40:53 -0500 Received: from eddie.linux-mips.org ([148.251.95.138]:48222 "EHLO cvs.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755166AbcBBTkv (ORCPT ); Tue, 2 Feb 2016 14:40:51 -0500 Date: Tue, 2 Feb 2016 19:40:48 +0000 (GMT) From: "Maciej W. Rozycki" To: Jeffrey Merkey cc: Steven Rostedt , linux-kernel@vger.kernel.org, Jason@zx2c4.com, aconole@redhat.com, Andrew Morton , andriy.shevchenko@linux.intel.com, linus.walleij@linaro.org, nicolas.iooss_linux@m4x.org, pmladek@suse.com, tj@kernel.org Subject: Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options In-Reply-To: Message-ID: References: <1454369752-20706-1-git-send-email-jeffmerkey@gmail.com> <1454369752-20706-4-git-send-email-jeffmerkey@gmail.com> <20160201205810.59250879@grimm.local.home> User-Agent: Alpine 2.20 (LFD 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 1 Feb 2016, Jeffrey Merkey wrote: > If a debugger is loaded it will not crash, just enter the debugger. > But yes, it will int3 if set and no debugger has been loaded to handle > the int3 condition. Hmmm. Maybe its better just to skip calling > pr_emerg and put this logic as a single call somewhere else. What's the point? If you have a debugger loaded, then surely you can just set a breakpoint anywhere you like using whatever user interface the debugger provides for setting breakpoints. You can actually set any number of software breakpoints you like wherever you like, depending on what you actually want to debug. I fail to see why it would have to be prearranged within the kernel -- do you have a configuration where you run the kernel from ROM by any chance? Maciej