wireshark-users-bounces@xxxxxxxxxxxxx wrote on 06/12/2006 14:28:33:
> It's more a question for the developer list, but since most of them are
> lurking here as well it may get the right attention.
>
OK, if I don't get any more replies I'll try there.
> I'm totally not into this generated dissector thing, but from the docs
it
> seems that idl2wrs is what you can use. See the wiki:
> http://wiki.wireshark.org/idl2wrs
>
It turns out that is just a script that calls omiidl, which is what
I was doing. It has made me realise I'm not calling it quite correctly.
So I now generate the .c file using :-
omniidl -p c:\wireshark-0.99.3a\tools -b wireshark_be q_quentinv3.idl >
packet-quentinv3.c
But I still get the problem.
Thanks for the help. Any more ideas anyone?
Andy Ling
> On Wed, 6 Dec 2006 Andy.Ling@xxxxxxxxxxx wrote:
>
> > I'm not sure if this is the right list, but I'll start here.
> >
> > I am having problems with a CORBA protocol plugin. I have generated
> > the .c file using something like :-
> >
> > omniidl -p c:\wireshark-0.99.3a -b ethereal_be q_quentinv3.idl >
> > packet-quentinv3.c
> >
> > and built and installed the .dll without problems.
> >
> > But when I enable the protocol analyser, any IDL method that doesn't
> > have any arguments is marked as [Malformed Packet: Q_QUENTINV3]
> > Those with arguments have the arguments decoded correctly and
> > are not marked with any error.
> >
> > If I disable my protocol analyser then no packets show errors.
> >
> > I'm using version 0.99.3a on Win2K
> >
> > Thanks for any help
> >
> > Andy Ling
> >
>
> _______________________________________________
> Wireshark-users mailing list
> Wireshark-users@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-users