On Thu, 2009-02-05 at 17:04 +0000, Ian Jackson wrote:
> handle SIGUSR2 nostop noprint
> break serial_ioport_write if (addr&7)==1
> cont
> * do whatever it is that makes the VM stuck
> * when it next stops it will be in serial_ioport_write setting
> the IER. So
> print val
> print *s
This breakpoint is triggered for all messages printed by the kernel,
which always showed up with no delay; but it is only occasionally
triggered for strings printed by userspace, even after forcing those
strings to show up by sending keystrokes.
Here is one of the latter cases. (I am sitting at a
“root@andersk-intrepid:~# ” prompt, repeatedly pressing Enter. Each
keypress causes the previous prompt to show up, followed by a newline,
and the current prompt is stalled.)
Breakpoint 1, serial_ioport_write (opaque=0xb342e0, addr=1, val=5)
at
/home/andersk/xen-3-3.3.1/debian/build/build-utils_amd64/tools/ioemu-dir/hw/serial.c:413
413 {
(gdb) print val
$5 = 5
(gdb) print *s
$6 = {divider = 1, rbr = 0 '\0', thr = 32 ' ', tsr = 32 ' ', ier = 5 '\005',
iir = 193 '�',
lcr = 19 '\023', mcr = 11 '\v', lsr = 96 '`', msr = 176 '�', scr = 0 '\0',
fcr = 129 '\201',
thr_ipending = 1, irq = 0xb1d610, chr = 0xb122a0, last_break_enable = 0, base
= 0,
it_shift = 0, baudbase = 115200, tsr_retry = 0, last_xmit_ts = 380482341502,
recv_fifo = {
data = '\r' <repeats 16 times>, count = 0 '\0', itl = 8 '\b', tail = 0
'\0',
head = 0 '\0'}, xmit_fifo = {data = "repid:~# rsk-int", count = 0 '\0', itl
= 0 '\0',
tail = 9 '\t', head = 9 '\t'}, fifo_timeout_timer = 0xb31ad0,
timeout_ipending = 0,
transmit_timer = 0xb31b00, char_transmit_time = 78120, poll_msl = -1,
modem_status_poll = 0xb327e0}
Anders
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home