Setting up oskit + oskit-mach source tree for debugging

I noticed my gdb isn't properly finding the oskit sources when I am stepping through the kernel. How should the source tree be arranged so that it works as expected? BTW: I allocated my 640MB IDE drive to oskit-mach since the problem with aic78xx seems formidable right now. That should enable me

Re: Setting up oskit + oskit-mach source tree for debugging

B. Douglas Hilton [EMAIL PROTECTED] writes: I noticed my gdb isn't properly finding the oskit sources when I am stepping through the kernel. How should the source tree be arranged so that it works as expected? Uhm, I don't know what's the cause of your problem, but did you have a look at the

Re: Setting up oskit + oskit-mach source tree for debugging

I think you misunderstood my question. I'm sure you know that gdb will display the source code of your program while you step through it. I am debugging the oskit-mach kernel, and I can follow the kernel source except when it calls an oskit function, I just wondered where the oskit source should

Re: Setting up oskit + oskit-mach source tree for debugging

I think you misunderstood my question. I'm sure you know that gdb will display the source code of your program while you step through it. I am debugging the oskit-mach kernel, and I can follow the kernel source except when it calls an oskit function, I just wondered where the oskit source