Hi to everyone. I'm not sure if this is the correct list to write to, but I wasn't able to find my answer anywhere else..
I compiled my 2.6.17.14 kernel with kgdb patches from cvs (i used the 2.6.17 tag) and all went well. I patched gdb 6.4 sources with the gdb-kgdb-module-notification.patch v1.3 and compiled it for mi target architecture (arm linux) When debugging kernel code there are no problems. I can put breakpoints in both C source code and assembly. But when debugging kernel modules I can only put them into assembly. I have used the command set solib-search-path to point to my modules directories When I load modules (or if they are already loaded) the symbols are correctly found (I think) Doing an 'info shared' gives From To Syms Read Shared Object Library 0xbf042000 0xbf0420fc Yes /usr/src/linux-2.6.17.14/drivers/i2c/busses/i2c-ep93xx.ko 0xbf03e000 0xbf03f230 Yes /usr/src/linux-2.6.17.14/drivers/i2c/algos/i2c-algo-bit.ko plus many more.. I can browse source code, but I'm not able to put breakpoints directly in the C code. The kernel has been compiled with the option CONFIG_DEBUG_INFO when doing 'list <somefunc>' - with the function being defined inside the module - gdb tells me it cannot find the line (or something similar). Sorry for not being very clear, but I don't have access to the output right now. I even tried with the gdb command add-symbol-file <somepath>/<mymodule>.ko 0x01234567 taking the address from cat /proc/modules to no avail. Did I miss anything? Thanks for your time. Any hint would be greatly appreciated! smazzux ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
