KSLD bug report: 32 bit causes target panic

Question

Since the bug report link:
http://soldc.sun.com/developer/support/driver/tools/KSLD/bug-report.html
goes to a non existant email address, I thought I would post here.
Setup:
ksld 1.01
target and host booted with kernel/unix (32 bit)
/proto directory struct as described in starting ksld doc
debugging ramd driver example
ramd directory:
drwxr-xr-x 4 root other 512 Feb 11 12:40 .
drwxr-xr-x 10 root other 512 Feb 11 12:47 ..
drwxrwxrwx 2 bin bin 512 Feb 11 10:26 777
-rw-r--r-- 1 root other 341 Feb 11 11:31 Makefile
-rw-r--r-- 1 root other 1610 Apr 24 2001 README
-rw-r--r-- 1 root other 3588 Apr 18 2001 install
lrwxrwxrwx 1 root other 52 Feb 11 10:47 misc -> /export/home/ksld-space/proto/root_sparc/kernel/misc
-rw-r--r-- 1 root other 2523 Apr 18 2001 ntestram.c
-rw-r--r-- 1 root other 2542 Apr 18 2001 printinfo.c
lrwxrwxrwx 1 root other 6 Feb 11 10:46 proto -> /proto
-rw-r--r-- 1 root other 25713 Feb 11 11:29 ramd.c
-rw-r--r-- 1 root other 291 Apr 18 2001 ramd.conf
-rw-r--r-- 1 root other 210 Apr 18 2001 ramio.h
drwxrwxrwx 4 bin bin 512 Feb 11 19:51 sparc
-rw-r--r-- 1 root other 1785 Apr 18 2001 testram.c
lrwxrwxrwx 1 root other 67 Feb 11 10:48 unix.281 -> /export/home/ksld-space/proto/root_sparc/platform/sun4u/kernel/unix
HOST output
home1# ksld -t hardwire unix.281 99
Reading unix.281
KSLD v1.0 on sun4u [SunOS 5.8]
Current thread is 0x4001fe60
Reading krtld
Reading genunix
Reading platmod
Reading SUNW,UltraSPARC-II
Reading specfs
Reading TS
Reading TS_DPTBL
Reading ufs
Reading fssnap_if
Reading rpcmod
Reading ip
Reading rootnex
Reading options
Reading sad
Reading pseudo
Reading sd
Reading scsi
Reading glm
Reading pcipsy
Reading dada
Reading todmostek
Reading procfs
Reading sockfs
Reading clone
Reading ip6
Reading tcp
Reading md5
Reading tcp6
Reading udp
Reading udp6
Reading icmp
Reading icmp6
Reading arp
Reading timod
Reading conskbd
Reading wc
Reading ebus
Reading su
Reading kb
Reading ms
Reading consms
Reading se
Reading elfexec
Reading fifofs
Reading ldterm
Reading ttcompat
Reading zs
Reading ptsl
Reading ptc
Reading rts
Reading tl
Reading keysock
Reading sysmsg
Reading cn
Reading pipe
Reading mm
Reading hme
Reading ufs_log
Reading doorfs
Reading devinfo
Reading iwscn
Reading log
Reading sy
Reading fctl
ksld_dbx: can't stat /platform/sun4u/kernel/drv/afb -- No such file or directory
Reading afb
ksld_dbx: can't open /platform/sun4u/kernel/drv/afb -- No such file or directory
Reading fd
Reading busra
Reading cs
Reading winlock
Reading seg_drv
Reading usba
Reading kstat
Reading vol
Reading cpc
Reading tnf
Reading pcihp
Reading hpcsvc
Reading pcicfg
Reading nfssrv
Reading nfs
Reading rpcsec
Reading tlimod
Reading seg_mapdev
Reading inst_sync
Reading mntfs
Reading tmpfs
Reading klmmod
Reading autofs
Reading connld
Reading bootdev
Reading shmsys
Reading ipc
Reading ramd
Reading kaio
detected a multithreaded program
t@0 stopped in (unknown) at 0xedd000d8
0xedd000d8: ta %icc,%g0 + 125
(ksld_dbx) module -v ramd.o
Module: ramd.o
Language: ansic
Debugging information: read [stabs version: 3.1]
Source file: /opt/SUNWddk/src/drivers/ramd/ramd.c
Object file: /opt/SUNWddk/src/drivers/ramd/sparc/obj32/ramd.o
Loadobject: /usr/kernel/drv/ramd
(ksld_dbx) stop in ram_strategy
(2) stop in ram_strategy
poll in failed
can't set breakpoint
TARGET output:
connected
New connection: uid 0, fd 7
Begin traceback... sp = edd48290
Called from edd009dc, fp=edd47b41, args=34 edd308ee eddc40a8 34 edd042f0 edd042ec
Called from edd03624, fp=edd47c11, args=fff74000 edda51f0 102d087a ffffffff91d0207e 0 4
Called from edd0c0d0, fp=edd47cd1, args=102d087a 91d0207e ff1bd714102d087a 100 edd48608 27
Called from edd0a394, fp=edd47d81, args=eddb7788 8 eddc16a1 f0000 1 ffff
Called from edd176d4, fp=edd47e31, args=ffff eddb7788 0 1 0 eddc1690
Called from edd0e470, fp=edd47f41, args=edd49058 0 0 3c 0 edda69d8
Called from edd0e214, fp=edd47ff1, args=eddb6d58 eddc1690 edd49158 ffffffffffffffff 10000 edd483e0
Called from edd0e154, fp=edd480a1, args=eddc1640 edda3550 0 0 0 0
Called from edd071b4, fp=edd48121, args=0 0 0 0 0 0
Called from 0, fp=0, args=0 0 0 0 0 0
End traceback...
abort jump: trap 34 sp edd48290 pc edd042ec npc edd042f0
etext edd308ee estack edd489a0 edata edda2388 nofault edda2658
ksld_kadb[0]: (`o403P0801So6mLD42d8N_lK^bH00004)(`o403P0801So6mLD42d8N_lK^bH0000
panic[cpu0]/thread=4001fe60: BAD TRAP: type=34 rp=4002fbc0 addr=40030507 mmu_fsr=0
sched: alignment error:
addr=0x40030507
pid=0, pc=0xedd2ba78, sp=0x4002fc50, tstate=0x1404, context=0x0
g1-g7: 1000c000, edda1f78, edda1f78, 0, edda2658, 14aef0, 4001fe60
panic: entering debugger (continue to save dump)
Trap 7d
What is wrong with the setup,when a breakpoint would cause a traceback and panic on the target?

Answer 1

One other possibility is having sufficient rights, especially if you are invoking it via some other app, rather than manually as a logged in user. If you are not logged in and instead invoke it via a web site action, I believe you will have problems reading the registry, accessing a desktop, writing to disk, etc.
Sorry I can't be more definitive, but perhaps it will help.
Please post your conclusion, if you find it.
--Ian