From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 kgdb without serial port
Date: Fri, 26 Dec 2003 19:27:40 +0100 [thread overview]
Message-ID: <20031226182740.GA10397@elf.ucw.cz> (raw)
In-Reply-To: <20031215223438.196295a8.akpm@osdl.org>
Hi!
> > 2.6 kgdb patches in -mm tree seem to contain kgdb-over-ethernet stuff,
> > but still require me to fill in serial port interrupt/address. Is
> > there easy way to make it work without serial port? [This notebook has
> > none :-(].
>
> That's a bit ugly, but things should still work OK? Give it some random
> UART address but specify an ethernet connection at boot time - the kgdb
> stub should never touch the UART.
I found out what was biting me: using 2.95 with kgdb is bad idea. 2.95
with kgdb means reboot just after uncompressing kernel -- pretty nasty
to debug. Please apply,
Pavel
PS: kgdb could use some code-style changes. Will you accept such
patches?
--- tmp/linux/arch/i386/kernel/kgdb_stub.c 2003-12-26 18:50:45.000000000 +0100
+++ linux/arch/i386/kernel/kgdb_stub.c 2003-12-26 18:41:58.000000000 +0100
@@ -121,6 +121,10 @@
#include <linux/inet.h>
#include <linux/kallsyms.h>
+#if __GNUC__ < 3
+#error Sorry, your GCC is too old to work with kgdb. (It works with 3.3.2)
+#endif
+
/************************************************************************
*
* external low-level support routines
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-12-26 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 20:06 2.6 kgdb without serial port Pavel Machek
2003-12-16 6:34 ` Andrew Morton
2003-12-16 10:30 ` crypto-loop + highmen -> random crashes in -test11 Soeren Sonnenburg
2003-12-16 11:40 ` Andrew Morton
2003-12-18 8:30 ` Soeren Sonnenburg
2003-12-16 22:45 ` bill davidsen
2003-12-26 18:27 ` Pavel Machek [this message]
2003-12-26 19:08 ` 2.6 kgdb without serial port Andrew Morton
2003-12-26 21:18 ` Martin J. Bligh
2003-12-27 10:30 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031226182740.GA10397@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox