[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RESEND] [PATCH] Use GDB 'O' packets for console output


  • To: Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>, Xen-Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Tue, 19 Sep 2006 08:27:09 +0100
  • Delivery-date: Tue, 19 Sep 2006 00:37:17 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbbvQQOQpG7MUewEdu9pgANk04WTA==
  • Thread-topic: [Xen-devel] [RESEND] [PATCH] Use GDB 'O' packets for console output

Sharing a single serial line between console and gdbstub isn't a mode we
particularly considered. Without something like this patch, I suppose
ordinary console output and gdb packets get mixed together on the line and
confuse the gdb session? Does gdb actually print out the console data with
your patch?

It's not nice to tell core serial code about the debugger. The switch
between raw output and output-via-gdbstub should be entirely in console.c.

 -- Keir

On 19/9/06 6:10 am, "Tony Breeds" <tony@xxxxxxxxxxxxxxxxxx> wrote:

> The remote serial protocol for GDB supports echoing program
> output.  This patch adds a new SERHND flag and hooks into serial_puts()
> to allow this to happen.  All XEN prtintk()s and dom0 console output
> will get sent to a remote GDB if it's attached and the serial console
> shares the same port.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.