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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4CAF19FA.7010206@windriver.com>
Date:	Fri, 08 Oct 2010 08:17:46 -0500
From:	Jason Wessel <jason.wessel@...driver.com>
To:	Elvis Dowson <elvis.dowson@....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

On 10/08/2010 05:41 AM, Elvis Dowson wrote:
> Hi Jason,
>                       I'm getting eclipse target time outs, I've attached link to the video here : http://drop.io/kgdbwe01
>   

Because you are using a serial link you certainly want to close any
related to extra data you don't need.   Not knowing a whole lot about
what the Eclipse plugin gdb does, it is hard to know if this was an
eclipse timeout or not.

If you add the following to your .gdbinit it will at least tell you what
happened at the end.

set remotelogfile /tmp/gdb_serial_log.txt

It would be good to know if eclipse timed out and it just detached from
the target, or if some command crashed gdb.  It is purely a guess, but
it is probably eclipse requesting lots of information and simply timing out.

> and then launched eclipse debugger. It loads the vmlinux file, and a bunch of junk characters keep appearing continuously on the telnet session. 
>
>   

The "junk" you speak of is simply the gdb serial traffic, it is answered
in the FAQ

http://git.kernel.org/?p=utils/kernel/kgdb/agent-proxy.git;a=blob;f=README.TXT
> After about a minute or so, Eclipse terminates the session saying that it timed out. You can see this in the video. I edited the video, in between to trim off the long wait, with the characters scrolling in the terminal session, to the point where it crashes.
>
>   

I would not expect the terminal session to crash.  If an oops is
printed, it means there is an internal kgdb problem.

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