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/
Home Products Support Community News


[Xen-devel] Xen GDB server and watchdog timeouts

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen GDB server and watchdog timeouts
From: Simon Kagstrom <simon.kagstrom@xxxxxx>
Date: Fri, 28 Apr 2006 09:53:03 +0200
Delivery-date: Fri, 28 Apr 2006 00:53:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Wanderlust/2.15.2 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.4 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)

I have some problems with gdbserver-xen and just wanted to check if
they are known. I start a domain paused and immediately attach
gdbserver to it, thereafter I set a breakpoint (which will hit in 30
or so seconds) and let the domain go. When I hit the breakpoint, I can
start single-stepping, but after stepping for a while, I get

    Watchdog has expired.  Target detached.

in gdb. I can get back into debugging by restarting gdbserver and
reattaching the debugger. I have done 'set watchdog 0' (infinite) in
gdb. Is there some known workaround for this problem?

// Simon

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Xen GDB server and watchdog timeouts, Simon Kagstrom <=