I solved the problem by writing a small patch for the 8250 driver
(solves the issue for me).
However, I noticed that kdb has no disassembly support now, so it is
pretty useless - you cannot use a debugger without examining the code!
(a C debugger must show you C code, asm debugger must show you
disassembly I think this is very logical). Is there any effort to have
disassembly working again with kdb?
On Tue, 2012-07-17 at 09:41 -0500, Jason Wessel wrote:
> On 07/16/2012 05:12 PM, Stefan Parlitz wrote:
> > Hi
> > I'm trying to use KDB with minicom, connected to serial port of a
> > VM.
> > Pressing ctrl-a f g does not activate KDB (it is correctly compiled
> > etc), instead only "g" appears in minicom.
> > I can enter KDB only by writing:
> > echo g > /proc/sysrq-trigger
> > then KDB prompt appears on the serial console and I can use it
> > normally (until "go").
> > any idea what is wrong?
> Please report questions and problems to the mailing list, and not me
> I am guessing that the sysrq trigger or break sequence is not working
> on your new kernel, either on the host or the target side.
> Not all rs232 devices support a break sequence. You also didn't
> specify a kernel version, what kind of target system you are using