2008/3/15, Andrew Hood <[EMAIL PROTECTED]>:
>
> Stig Bjørlykke wrote:
> > On 13. mars. 2008, at 15.51, Peter Johansson wrote:
> >
> >> Could this then be of the same type of issue that is with adns,  hence
> >> it is required to recompile libsmi too if using another  compiler for
> >> Wireshark on Windows than MSVC 6. Developer Studio  2005EE for
> instance?
> >
> >
> >
> > Does it work correctly on win32 with user specified MIBs without
> > running in the debugger?
> > Or do we have to make some changes before releasing 1.0?  Like revert
> > r24569 and live with the memory leakage?
> >
> > I'm getting crashes on win32 with 0.99.8 having a custom MIB with
> > duplicated DESCRIPTION field (attached), so we probably have some more
> > issues using libsmi...
>
> Does your custom MIB work if you define it as attached?
> If it does it might be a libsmi bug.
>
> --
> There's no point in being grown up if you can't be childish sometimes.
>                -- Dr. Who
>
> MY-MIB DEFINITIONS ::= BEGIN
>
> IMPORTS
>        MODULE-IDENTITY, enterprises
>        FROM SNMPv2-SMI
>        ;
>
> myValues MODULE-IDENTITY
>        LAST-UPDATED "200802270000Z"
>        ORGANIZATION "Private"
>        CONTACT-INFO "Stig"
>        DESCRIPTION  "My Description"
>        REVISION     "200802270000Z"
>        DESCRIPTION  "Version 1.0"
>        ::= { thalesNorwayAS 4 }
>
> thalesNorwayAS OBJECT IDENTIFIER ::= { enterprises 3752 }
>
> END
>
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@wireshark.org
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>
There are more (multiple) recent versions of libsmi than 0.4.5, why was
0.4.5 choosen (perhaps because it was the one that was available at the time
of introduction).
Should a newer version of the library be considered? This might help with
some of the crashes, it will not however address the double free calls (on
Windows).

/ Peter
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev

Reply via email to