weird remote debug problem

Matthew Dillon dillon at
Thu Oct 14 12:43:31 PDT 2004

:I'm trying to track down what I think is a bug in bus_dmamem_alloc()
:using kgdb over a serial line and am having problems with break
:After loading my driver, sending a BREAK over the comconsole drops me
:into gdb. I set a break point on bus_dmamem_alloc and continue. Then,
:I send an ioctl to the driver to trigger memory allocation and think
:that the break point has triggered because the below shows in the
:CPU1 stopping CPUs: 0x00000001
: stopped
:but gdb hasn't triggered. Has anyone seen this before? Any ideas? Tnx!
:Chuck Tuffli
:Agilent Technologies

    It's quite possible that gdb's breakpoint feature is broken in 
    current kernels.  There have been a lot of changes and I don't think
    anyone has actually tried to use the feature in the last year except
    you, just now.

    What I suggest is that you just throw a lot of printf()'s into the
    code.  That's what I do, mostly.

					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>

More information about the Kernel mailing list