Subject: port-xen/36671: DB cannot show symbol name if it runs on xen-3.1.0
To: None <,,>
From: None <>
List: netbsd-bugs
Date: 07/21/2007 00:50:00
>Number:         36671
>Category:       port-xen
>Synopsis:       DB cannot show symbol name if it runs on xen-3.1.0
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-xen-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 21 00:50:00 +0000 2007
>Originator:     Jam
>Release:        NetBSD 4.99.24
System: NetBSD fs 4.99.24 NetBSD 4.99.24 (XEN3_DOM0) #0: Sat Jul 21 08:13:56 JST 2007 jam@fs:/mnt/raid/netbsd/20070719t1/src/sys/arch/i386/compile/XEN3_DOM0 i386
Architecture: i386
Machine: i386
	Put a kernel to /stand/20070719t1/netbsd-XEN3_DOM0.
	Make a hard likt to it at /netbsd.
	Run NetBSD and stop it.  Type "trace" to get a trace log.

	With Xen-3.0.4, DB can show symbol name fine.

	With Xen-3.1.0, DB cannot show symbol name.
	It shows following.  (First "test crash" message
	is what I put in.  I cannot send break signal through
	serial console, so I added 'panic("test crash");' at the
	very beginning of kernel.)

panic: test crash
Stopped in pid 0.1 (system) at  0xc04bb6c4:     popl    %ebp
db> trace
?(c085ef35,c0a08a84,c0a08a78,c04393ac,d) at 0xc04bb6c4
?(c086559e,c08d0e60,2,c08c6070,c08416c6) at 0xc0439515
?(c125df80,c140d280,c0a08ae8,c0a08af4,c0a08ae8) at 0xc0662e78
?(c125df80,c08c5fb0,c0a08af4,c0a08ae8,c065dfd0) at 0xc042eea6
?(cae4ac74,c125df80,9,c125df80,0) at 0xc065f4d5
?(c065f470,c125df80,0,c125df80,c125df80) at 0xc0659835
?(c125df80,c0a08b78,c0a08b74,c043981c,d) at 0xc065f38b
?(0,c125df80,0,c042da2e,c0823aaf) at 0xc04f4486
?(0,c08c5080,0,0,0) at 0xc042eea6
?(0,c08c5080,0,0,c0a05c10) at 0xc042ef6c
?(c0823aaf,0,c0a08c28,c042f233,c094b4a4) at 0xc042f0f4
?(c094b4a4,2,0,0,c09778dc) at 0xc04ba4d6
?(c0913d00,1,c0a74088,c0a08c4c,c04cbe29) at 0xc042f233
?(c01001df,c01001e7,0,0,0) at 0xc03f7e2f

	Install xenkernel3, xentools3, xentools3-hvm.
	Install compiled recent netbsd kernel with XEN3_DOM0 config.
	I got this problem on netbsd-4.99.22 and 4.99.24.

	Run netbsd-XEN3_DOM0 on Xen-3.1.0.
	Send break signal to run DB.
	Type "trace" on DB.
	No idea.