linux-kernel - Re: Break point not hit while debugging linux kernel with kgdb

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 09 Jun 2012 22:48:31 +0400
From:	Sergei Shtylyov <sshtylyov@...sta.com>
To:	Anil Nair <anilcoll90@...il.com>
CC:	prasannatsmkumar <prasannatsmkumar@...il.com>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: Break point not hit while debugging linux kernel with kgdb

Hello.

On 06/09/2012 10:23 PM, Anil Nair 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.

    Yeah, KGDB was accepted into kernel exactly for more "poorly fixed patches" 
to appear. :-)

>> 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

    gdbserver is only good for debugging the applications.

WBR, Sergei
--
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/