Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755567Ab2FISXm (ORCPT ); Sat, 9 Jun 2012 14:23:42 -0400 Received: from mail-ob0-f174.google.com ([209.85.214.174]:61751 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753417Ab2FISXl (ORCPT ); Sat, 9 Jun 2012 14:23:41 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 9 Jun 2012 23:53:40 +0530 Message-ID: Subject: Re: Break point not hit while debugging linux kernel with kgdb From: Anil Nair To: prasannatsmkumar Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1119 Lines: 32 Hi Prasanna, On Mon, May 28, 2012 at 3:46 PM, prasannatsmkumar wrote: > Hi, > > I tried to debug the linux kernel with kgdb (over serial port). The Maintainers would never recommend the use of a debugger, it results in poorly fixed patches. > I have > configured the host and target machines and I am able to connect, step > in the kernel code. In gdb I gave "break usb_register_dev" and "break > usb_deregister_dev" and continued the execution (continue in gdb). > Once the desktop is up, I connected a USB device (first tried with USB > keyboard). Break point was not hit. I tried some more functions and > break points are never hit. What should I do for it? Am I missing > something? You have to use gdbserver for connecting target and host systems i guess. You may find many tutorials about it on the internet. -- Regards, Anil Nair -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/