Wireshark-dev: Re: [Wireshark-dev] Dissectors generated using ASN.1 tool asn2ws could not be co
From: Zongjun <[email protected]>
Date: Tue, 27 Nov 2007 17:37:21 -0800
Problem solved!

I am trying to switch back to 0.99.5 release, since it is selected by my work group.  It turned out I was using the file autogerated by asn2wr coming with 0.99.6 release, which create the following extra codes inside the "dissect_xxx_PDU()" function:
   asn1_ctx_t asn1_ctx;
   asn1_ctx_init(&asn1_ctx, ASN1_ENC_BER, TRUE, pinfo);
Also, with 0.99.5, the tool refers to <epan/asn1.h>, which should be <plugins/asn1/asn1.h>

Regards,
Zongjun

On Nov 27, 2007 1:52 PM, Zongjun <[email protected]> wrote:
Hi All,

I have a working dissector generated using ASN.1 tool asn2wr.  But it is a pain each time when ASN.1 specification changes, we have to recompile the whole Wireshark source codes.  Therefore, I am trying to change into plug-in approach.

I am following exactly the steps listed in README.plugin file.  But I am getting lots of compilation errors, including couldn't find <epan/asn1.h> and "packet-ber.h" ,which is easy to fix;  and 1000+ asn.1 errors, which I have no idea.  I searched the directory structure of Wireshark release, as well as dev-maillist, it seems to me so far nobody has tried to change a asn.1 generated dissector into a plug-in.  We either go epan/dissector way, or go plugins/ way.  And asn.1 protocols are only go epan/dissector way.

Am I miss something here?

Thanks,
Zongjun



--
Thanks,
Zongjun