WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

[XenPPC] gdb stub packet size

To: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Subject: [XenPPC] gdb stub packet size
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Fri, 14 Apr 2006 11:15:55 -0500
Delivery-date: Fri, 14 Apr 2006 09:14:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
Has anybody used the Xen gdb stub recently? GDB is complaining that the
"all registers" response packet is too large, and sure enough it should
be over 1KB (32 GPRs + 32 FPRs at 16 ASCII bytes each = 1KB). I can't
figure out how this broke, or how it worked before...

I'm using GDB 6.3.50.20050818, which as I recall has a limit of
something like 400 bytes on incoming packets. I recently ran into this
issue on the RISCWatch stub with large memory reads.

-- 
Hollis Blanchard
IBM Linux Technology Center


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

<Prev in Thread] Current Thread [Next in Thread>
  • [XenPPC] gdb stub packet size, Hollis Blanchard <=