Wireshark-dev: Re: [Wireshark-dev] BER ASN1 generated dissectors update?
From: "Kukosa, Tomas" <tomas.kukosa@xxxxxxxxxxx>
Date: Sat, 20 Oct 2007 17:47:19 +0200
Hello Graeme, use following: #.FN_BODY BuiltInContentType/_untag ... #.END Let me know if you meet any other problem. Regards, Tomas ________________________________ Od: wireshark-dev-bounces@xxxxxxxxxxxxx za uživatele Graeme Lunt Odesláno: so 20.10.2007 16:27 Komu: 'Developer support list for Wireshark' Předmět: Re: [Wireshark-dev] BER ASN1 generated dissectors update? Anders, I am trying to use -X -T flags with the x411 dissector. I need to move some of my code in the conformance file for the dissect_x411_<TYPE> function to the dissect_x411_<TYPE>_U function (as that is where the data is now actually handled). (The actual type I have the problem with is BuiltInContentType). If I just add _U to the function name in the FN_BODY declaration, then the whole FN_BODY is ignored by asn2wrs. I also tried using an FN_VARIANT = _U, with no success. Any pointers on should I go about changing the conformance file? Graeme > -----Original Message----- > From: wireshark-dev-bounces@xxxxxxxxxxxxx > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of > Anders Broman > Sent: 18 October 2007 10:22 > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] BER ASN1 generated dissectors update? > > > > >Just to be clear, could you give an example of the type of > "workarounds" that can be removed from each of these two >locations? > > For the -T option an example from SNMP: > --- snip --- > #.FN_BODY PDUs/get-request > gint8 class; > gboolean pc, ind_field; > gint32 tag; > guint32 len1; > > if(!implicit_tag){ > /* XXX asn2wrs can not yet handle tagged assignment yes so this > * XXX is some conformance file magic to work around that bug > */ > offset = get_ber_identifier(tvb, offset, &class, &pc, &tag); > offset = get_ber_length(tvb, offset, &len1, &ind_field); > } > --- snip --- > For the ambitious looking at DAP there is commented ASN1 > code, this code > *should* work uncommented now... > The EXTERNAL type should also be handled by asn2wrs now (may require > some hand coding). > Regards > Anders > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@xxxxxxxxxxxxx > http://www.wireshark.org/mailman/listinfo/wireshark-dev > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@xxxxxxxxxxxxx > http://www.wireshark.org/mailman/listinfo/wireshark-dev > _______________________________________________ Wireshark-dev mailing list Wireshark-dev@xxxxxxxxxxxxx http://www.wireshark.org/mailman/listinfo/wireshark-dev
<<winmail.dat>>
- References:
- Re: [Wireshark-dev] BER ASN1 generated dissectors update?
- From: Graeme Lunt
- Re: [Wireshark-dev] BER ASN1 generated dissectors update?
- Prev by Date: [Wireshark-dev] comment on...
- Next by Date: [Wireshark-dev] design problem
- Previous by thread: Re: [Wireshark-dev] BER ASN1 generated dissectors update?
- Next by thread: Re: [Wireshark-dev] BER ASN1 generated dissectors update?
- Index(es):
- Get Wireshark
- Download
- Code of Conduct