linux-kernel - Re: kgdb errors with serial console

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 08 Oct 2010 03:07:58 +0400
From:	Elvis Dowson <elvis.dowson@....com>
To:	Jason Wessel <jason.wessel@...driver.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux OMAP Mailing List <linux-omap@...r.kernel.org>
Subject: Re: kgdb errors with serial console

Hi Jason,

On Oct 8, 2010, at 2:37 AM, Jason Wessel wrote:

> It would probably also be good to test if the debugger is working at all
> on your serial port.
> 
> Configure the debugger with:
> # echo ttyS2 > /sys/module/kgdboc/parameters/kgdboc
> kgdb: Registered I/O driver kgdboc.
> # echo g > /proc/sysrq-trigger
> SysRq : DEBUG
> 
> And now to exit debugger you must blindly and perfectly type
> $D#44+
> 
> Nothing will be echoed because at this stage the kernel serial polling
> driver would just be collecting characters.
> 
> After typing that the kernel should return back to the running state and
> print something like:
> +$OK#9a#

Cool, I tried all the commands that you suggested and it worked perfectly. I got the same outputs. 

So, if I understand correctly, I boot into the kernel without the kgbdwait option, and then manually launch the kgdb and then connect from Eclipse using gdb.

The system waits at the root login prompt. 

Just so that I can see some quick results, can you suggest which file I could set a break point into, and monitor the registers and variable states at this stage, i.e. immediately after the root login?

Best regards,

Elvis

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