kdb: Avoid using dbg_io_ops until it is initialized

This fixes a bug with setting a breakpoint during kdb initialization
(from kdb_cmds).  Any call to kdb_printf() before the initialization
of the kgdboc serial console driver (which happens much later during
bootup than kdb_init), results in kernel panic due to the use of
dbg_io_ops before it is initialized.

Signed-off-by: Tim Bird <tim.bird@am.sony.com>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
This commit is contained in:
Tim Bird 2011-09-21 13:19:12 -07:00 committed by Jason Wessel
parent bec4d62ead
commit b8adde8dde

View File

@ -689,7 +689,7 @@ int vkdb_printf(const char *fmt, va_list ap)
if (!dbg_kdb_mode && kgdb_connected) { if (!dbg_kdb_mode && kgdb_connected) {
gdbstub_msg_write(kdb_buffer, retlen); gdbstub_msg_write(kdb_buffer, retlen);
} else { } else {
if (!dbg_io_ops->is_console) { if (dbg_io_ops && !dbg_io_ops->is_console) {
len = strlen(kdb_buffer); len = strlen(kdb_buffer);
cp = kdb_buffer; cp = kdb_buffer;
while (len--) { while (len--) {