Messages in this thread | | | Date | Sat, 27 Dec 2003 11:30:30 +0100 | From | Pavel Machek <> | Subject | Re: 2.6 kgdb without serial port |
| |
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, > > I've been using 2.95.3 on and off for ages, no problems?
Strange... Okay, some details. If I use gcc-2.95.4 (from debian) by setting GCC = gcc-2.95, it crashes very early during boot. So perhaps it dislikes "crosscompiling" instead of specific gcc version? [I was doing that to speed compiles up]. Pavel
> Spose so. The kgdb stub really needs a serious reorganisation so that > non-ia32 architectures can share generic things. And general reduction of > the patch footprint, maybe some feature removal too. A fairly large job.
Yes, and as I need kgdb on x86-64...
-- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |