It's no different from debugging any other program, so you can read any introduction to debugging.
On Wed, Feb 11, 2015 at 11:58:37AM +0500, david jhon wrote: > I have been striving hard lately to debug openvswitch after building it > from source on Ubuntu 14.04, but still not successful. Could you please > suggest me some document or link which might be helpful for a noob to get > his hands dirty on ovs debugging and development. > > Waiting for your response................... > > On Tue, Feb 3, 2015 at 9:51 PM, Ben Pfaff <[email protected]> wrote: > > > On Tue, Feb 03, 2015 at 12:12:09AM +0500, david jhon wrote: > > > Hi Ben, > > > > > > Thanks for your response. > > > > > > It means that after setting up a break point at cmd_show() method and > > > attaching gdb to ovsdb-server pid (i.e., gdb ovs-vsctl.o > > > --pid=ovsdb-serverpid), I am not able to debug this specific file as > > single > > > stepping results in the following output: > > > (gdb) n > > > Single stepping until exit from function __kernel_vsyscall, > > > which has no line number information. > > > Warning: > > > Cannot insert breakpoint 1. > > > Cannot access memory at address 0x9353 > > > > > > please guide me what I am doing wrong. how gdb can be used to debug > > > openvswitch. Thank you! > > > > That's not anything OVS-specific. It means that you can't single-step > > into a system call. If you need more information, then please ask about > > it on a GDB or Linux-kernel mailing list. > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
