linux-kernel - Re: kgdboe?

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:	Tue, 6 May 2008 15:16:32 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Jason Wessel <jason.wessel@...driver.com>,
	lkml <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: kgdboe?

* Jesse Barnes <jbarnes@...tuousgeek.org> wrote:

> So when will we see kgdboe or some other way of getting gdb to connect 
> to the target over ethernet upstream?

i think the proper way would be to extend the kgdb-over-console (kgdboc) 
concept and make it easy to utilize the existing netconsole code via 
KGDB. This brings nice synergy: netconsole is utilized by other debug 
infrastructure as well so anything that supports netconsole would 
automatically support KGDB as well. I dont really like the old kgdboe 
approach from a design POV as it created a parallel infrastructure for 
special-purpose kgdb IO.

likewise, the firewire debugging code could/should be extended to create 
a bidirectional console as well - that has other benefits as well. (we'd 
get printks over firewire - instead of the special-purpose firescope 
utility)

and the early console drivers could be reused to do early debugging via 
KGDB as well.

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