It depends when you think it got broken. I built a CORBA dissector using 2.2.5. I haven’t tried the latest build though.
I’m using Windows 7. Generally I don’t actually use the idl2wrs script. I use commands based on it. So to generate the .c files I use something like..
C:\Python27\omniorb\omniORB-4.1.6\bin\x86_win32\omniidl.exe -p C:\wireshark-2.2.5\tools -b wireshark_be myCorba.idl > packet-myCorba.c
HTH
Andy Ling
From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]
On Behalf Of Michael Mann
Sent: Mon 26 June 2017 13:17
To: wireshark-dev@xxxxxxxxxxxxx
Subject: Re: [Wireshark-dev] Building CORBA dissectors
I'm guessing you didn't get a response because no one is building CORBA dissectors outside of the 3 or 4 that are in the source tree.
Those are generated with idl2wrs, but then the C output is part of source control (partially because I'm not sure all platforms could generate the C dissector as part of the build process).
If the CORBA dissectors that are currently in Wireshark source don't generate correctly, I can certainly take a look. But if you have
"private" CORBA dissectors, we may need to chat offline if you can't share them publically. Otherwise the preferred solution would be to provide your CORBA dissector (and sample capture) in a bug report in Bugzilla.
