I wouldn't expect ddb to work with 1.5.  You can find the relevant
changes to -current by looking at the cvs repository or the
source-changes logs for the following revisions:

    cvs rdiff -r1.4 -r1.5 syssrc/sys/arch/powerpc/powerpc/db_memrw.c
    cvs rdiff -r1.10 -r1.11 syssrc/sys/arch/powerpc/include/db_machdep.h
    cvs rdiff -r1.14 -r1.15 syssrc/sys/arch/powerpc/powerpc/db_interface.c
    cvs rdiff -r1.93 -r1.94 syssrc/sys/dev/usb/usbdi.c
    cvs rdiff -r1.15 -r1.16 syssrc/sys/arch/powerpc/powerpc/db_interface.c
    cvs rdiff -r1.14 -r1.15 syssrc/sys/arch/powerpc/powerpc/db_trace.c
    cvs rdiff -r1.15 -r1.16 syssrc/sys/arch/powerpc/powerpc/db_trace.c
    cvs rdiff -r1.41 -r1.42 syssrc/sys/arch/macppc/macppc/locore.S
    cvs rdiff -r1.18 -r1.19 syssrc/sys/arch/macppc/dev/akbd.c
    cvs rdiff -r1.16 -r1.17 syssrc/sys/arch/macppc/dev/pm_direct.c
    cvs rdiff -r1.19 -r1.20 syssrc/sys/arch/macppc/dev/adb_direct.c

Darrin

Derek Peschel <dpeschel@eskimo.com> writes:

> > A lot of issues with both the keyboard and ddb have been fixed in the
> > last couple of weeks.  If this is still a problem with -current
> > sources updated today, please file a bug report with send-pr.
> 
> I should have mentioned that I'm running 1.5.
> 
> I glanced at the ddb directory before posting and didn't see any changes
> relating to the kebyoard.  Can you give me more information?
> 
> As for the keyboard code, I've been keeping an eye on those changes, as well
> as writing some new code.  It's almost ready to be tested.
> 
> -- Derek