Looks like what I need. What's the quickest way to enable valgrind? I found this: http://openvswitch.org/pipermail/discuss/2013-May/010113.html
Does it still apply to today? Where can I define OVS_CTL_OPTS? Ben Pfaff <b...@ovn.org> escreveu no dia quinta, 3/03/2016 às 18:16: > On Thu, Mar 03, 2016 at 05:54:42PM +0000, André Mantas wrote: > > Hi again. > > > > For now, I'm testing the implementation with a floodlight controller that > > opens a bundle, adds a packet_out message and tries to commit the bundle. > > I'm using mininet to start a simple topology with 1 switch and 2 hosts > and > > connect the switch to the remote controller. I followed INSTALL.md to > start > > ovs before running the mininet script. > > > > Everything works like before if the controller does not send a packet_out > > in a bundle. However, when I try to send the packet_out to the bundle, > the > > switch disconnects from the controller after the commit request message > is > > sent and all ovs-ofctl commands fail on that bridge. > > > > To debug, I added some VLOG_INFO calls in handle_bundle_add and > > do_bundle_commit functions. The prints (found in /var/log/syslog) are > below > > together with the output of "ovs-ofctl snoop s1" > > > > Looks like adding the message to the bundle and committing the bundle is > ok > > but something happens afterwards? > > Where would be a good place to look for the problem? > > Usually when I get an unexpected connection close while debugging, it > means that ovs-vswitchd crashed. I recommend enabling core dumps and > then running GDB on the core. "valgrind" is also a good approach. > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
