Bug 189838 - net/openvswitch 1.7.1 : ovsdb-tool create segfaults
Summary: net/openvswitch 1.7.1 : ovsdb-tool create segfaults
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Kevin Lo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-15 15:20 UTC by chloe.desoutter@atasta.net
Modified: 2015-09-03 05:41 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description chloe.desoutter@atasta.net 2014-05-15 15:20:00 UTC 
After installing openvswitch from either pkg or ports, running ovsdb-tool create causes a segmentation fault.

Here is the GDB output
root@cabron:~ # gdb /usr/local/bin/ovsdb-tool
[snip]
(gdb) run create
Starting program: /usr/local/bin/ovsdb-tool create
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100471]
(no debugging symbols found)...[New Thread 802006400 (LWP 100471/ovsdb-tool)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 802006400 (LWP 100471/ovsdb-tool)]
0x000000000041c933 in ?? ()

Fix: 

Strangely when building with WITH_DEBUG=yes ovsdb-tool create will work just fine (but this doesn't help me identify where the bug hides).
How-To-Repeat: * Install openvswitch from either ports or pkg.
(Ports dependencies are built all with their default options.)
* Run ovsdb-tool create
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2014-05-15 16:01:41 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->emaste

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2015-09-03 03:27:45 UTC 
Over to current maintainer.
Comment 3 Kevin Lo freebsd_committer freebsd_triage 2015-09-03 05:41:28 UTC 
I believe this problem is fixed in the OVS 2.3.2.  Please update the ports
tree, thanks.