Re: [ovs-dev] debugging "make check" failures

2012-06-27 Thread ravi kerur
Never mind, I figured it out. Thanks for the inputs. On Wed, Jun 27, 2012 at 11:11 AM, ravi kerur wrote: > Thanks Ethan. Core file generation is enabled. However, I do not see > any core files under failed test directory i.e > tests/testsuite.dir/0449. Is the generated core file available in that

Re: [ovs-dev] debugging "make check" failures

2012-06-27 Thread ravi kerur
Thanks Ethan. Core file generation is enabled. However, I do not see any core files under failed test directory i.e tests/testsuite.dir/0449. Is the generated core file available in that directory or some place else? or it could be that ovs-vswitchd didn't segfault at all? openvswitch# ulimit -a c

Re: [ovs-dev] debugging "make check" failures

2012-06-26 Thread Ethan Jackson
Make sure you've enabled core files ulimit -a ulimit -c unlimited Ethan On Tue, Jun 26, 2012 at 5:49 PM, ravi kerur wrote: > Thanks Ben, I don't remember seeing core file under > tests/testsuite.dir/0449 directory. I will double-check, if its > available it will be definitely helpful. > > On Tu

Re: [ovs-dev] debugging "make check" failures

2012-06-26 Thread Chris Wright
* ravi kerur (rke...@gmail.com) wrote: > Thanks Ben, I don't remember seeing core file under > tests/testsuite.dir/0449 directory. I will double-check, if its > available it will be definitely helpful. Core file creation might be disabled (check ulimit). ___

Re: [ovs-dev] debugging "make check" failures

2012-06-26 Thread ravi kerur
Thanks Ben, I don't remember seeing core file under tests/testsuite.dir/0449 directory. I will double-check, if its available it will be definitely helpful. On Tue, Jun 26, 2012 at 5:10 PM, Ben Pfaff wrote: > On Tue, Jun 26, 2012 at 05:08:43PM -0700, ravi kerur wrote: >> The problem is that ovs-v

Re: [ovs-dev] debugging "make check" failures

2012-06-26 Thread Ben Pfaff
On Tue, Jun 26, 2012 at 05:08:43PM -0700, ravi kerur wrote: > The problem is that ovs-vswitchd crashes when eth_type = 0x8847/0x8848 > and happens only in the automation i.e "make check", or "make > dist-check", since user-space code has been successfully tested > manually and I couldn't find a way