Hi,
That would be a good idea. This is the files I have found that include
asn1.h
And a link to an ASN1 spec. where I have found one:
packet-ansi_map.c - Started to look at it but no ASN.1 file is
avalable(?) one has to be made by hand, needs BER SET.
packet-cops.c - RFC2748 & COPS-PR extension RFC3084
packet-ldap.c - RFC 1777 (LDAP v2), RFC 2251 (LDAP v3), and RFC 2222
(SASL).
http://www.itu.int/ITU-T/asn1/database/ietf/rfc/rfc2251/index.html
packet-pres.c - ISO 8823 OSI Presentation Protocol packets
http://www.itu.int/ITU-T/asn1/database/itu-t/x/x226/index.html
packet-snmp.c
packet-spnego.c - RFC 2478
Brg
Anders
-----Ursprungligt meddelande-----
Från: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] För Gerald Combs
Skickat: den 15 augusti 2005 22:35
Till: Ethereal development
Ämne: Re: [Ethereal-dev] Re: Memory allocation audit, janitor
project,EMEMification of dissectors
Looks good. Should we add a similar page for dissectors that use the
old-style ASN.1 code?
ronnie sahlberg wrote:
> ok, a wiki page for ememification created containing a list of all
> dissectors that use g_malloc().
>
> feel free to grep for other g_ functions allocating memory as well and
> add sections for them.
>
>
>
> On 8/14/05, Joerg Mayer <jmayer@xxxxxxxxx> wrote:
>
>>On Sun, Aug 14, 2005 at 02:23:38AM -0400, ronnie sahlberg wrote:
>>
>>>Gerald, what about an ethereal-janitor sub project and mailing list?
>>
>>I don't think a separate ml should be used. ethereal-dev is just fine.
>>
>>
>>>Anyone want to chip in? There are still 140 g_malloc()s left in
>>>epan/dissectors and if my current experience is worth anything
>>>probably half of them will have obvious memleaks (i.e. never g_free())
>>>and virtually all the others have non-obvious ones (exception raised
>>>between g_malloc() and g_free() and no CLEANUP_PUSH or simiar kludge)
>>>
>>>
>>>raise your hand if you want to help out, its pretty boring work but
>>>should really be done.
>>
>>I can start doing that. Maybe you can create a page in wiki and put in a
>>list of files that you already have looked at just to coordinate things.
>>Alternatively, that could be managed via a bugzilla entry but I think
>>that wiki is a much more efficient interface for this.
>>
>> ciao
>> Joerg
>>
>>--
>>Joerg Mayer <jmayer@xxxxxxxxx>
>>We are stuck with technology when what we really want is just stuff that
>>works. Some say that should read Microsoft instead of technology.
>>
>>_______________________________________________
>>Ethereal-dev mailing list
>>Ethereal-dev@xxxxxxxxxxxx
>>http://www.ethereal.com/mailman/listinfo/ethereal-dev
>>
>
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev