OK, thank you... this is very weird. You said you applied some changes
in the dissectors in order to compile without the warnings. Could you
send them so that I can test them here? This way I'll be sure if it's
a Linux issue or a dissector issue.
best regards,
--
--
:: Breno Jacinto ::
:: breno - at - gprt.ufpe.br ::
:: FingerPrint ::
2F15 8A61 F566 E442 8581
E3C0 EFF4 E202 74B7 7484
:: Persistir no difícil é a única maneira de torná-lo fácil algum dia. ::
2008/10/21 Maynard, Chris <Christopher.Maynard@xxxxxxxxx>:
> Yes, all 3 show up in the protocols list. But I'm currently having some unrelated trouble with the latest SVN, so I was only able to test it against Wireshark 1.0.3. And keep in mind that I'm working on Windows XP, not Linux.
>
> - Chris
>
>> -----Original Message-----
>> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
>> bounces@xxxxxxxxxxxxx] On Behalf Of Breno Jacinto
>> Sent: Tuesday, October 21, 2008 1:12 PM
>> To: Developer support list for Wireshark
>> Subject: Re: [Wireshark-dev] Installing a new dissector
>>
>> Hello Christopher,
>>
>> Did you check if the dissector shows up after you install it?
>> Because if it's ok for you, then I should try on another
>> system/configuration.
>>
>> best regards,
>>
>> --
>> :: Breno Jacinto ::
>> :: breno - at - gprt.ufpe.br ::
>> :: FingerPrint ::
>> 2F15 8A61 F566 E442 8581
>> E3C0 EFF4 E202 74B7 7484
>> :: Persistir no difícil é a única maneira de torná-lo fácil algum dia. ::
>>
>>
>>
>> 2008/10/20 Breno Jacinto <breno@xxxxxxxxxxxxxxx>:
>> > Hello,
>> >
>> > Yes, on my system it is also compiling and linking fine as well
>> > (with some warnings). But, the mistery is why is it not showing up in
>> > the Protocol list, as it is supposed to be? Also, since packets are
>> > not being dissected, they are just shown as a "data" after the layer 2
>> > header.
>> >
>> > best regards,
>> >
>> > --
>> > --
>> > :: Breno Jacinto ::
>> > :: breno - at - gprt.ufpe.br ::
>> > :: FingerPrint ::
>> > 2F15 8A61 F566 E442 8581
>> > E3C0 EFF4 E202 74B7 7484
>> > :: Persistir no difícil é a única maneira de torná-lo fácil algum dia.
>> ::
>> >
>> >
>> >
>> > 2008/10/20 Maynard, Chris <Christopher.Maynard@xxxxxxxxx>:
>> >> While there have been many changes since Ethereal, the use of
>> etype_vals and ethertype are not among them. They are both declared in
>> epan/dissectors/packet-ethertype.c and several other dissectors reference
>> them with no problems, so there is another reason why Wang Jing
>> encountered problems. I made some quick changes to your dissectors to
>> eliminate the warnings and it compiles and links just fine.
>> >>
>> >> By the way, I suggest (re-)reading README.developer and the related
>> README files in the doc/ directory if you want to know more about
>> Wireshark specifics.
>> >>
>> >>> -----Original Message-----
>> >>> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
>> >>> bounces@xxxxxxxxxxxxx] On Behalf Of Breno Jacinto
>> >>> Sent: Monday, October 20, 2008 8:19 AM
>> >>> To: Developer support list for Wireshark
>> >>> Subject: Re: [Wireshark-dev] Installing a new dissector
>> >>>
>> >>> Hello,
>> >>>
>> >>> 2008/10/19 WangJing <wj.vivian@xxxxxxxxx>:
>> >>> >
>> >>> > I fix this kind of error, and compile. But I still got the following
>> >>> error.
>> >>> > I think the code is used for Ethereal,
>> >>> > and the code is not compliant to Wireshark version..
>> >>>
>> >>> Yes, exactly, that is what I was suspecting from the beginning. The
>> >>> code was written for ethereal, so, there were changes in wireshark
>> >>> that made it incompatible somehow? Is there any documentation on what
>> >>> has changed and how to make Ethereal dissectors run on Wireshark?
>> >>>
>> >>>
>> >>>
>> >>> >
>> >>> > link -dll /out:adh.dll /NOLOGO /INCREMENTAL:no /MACHINE:I386
>> >>> /DEBUG
>> >>> > pack
>> >>> > et-adh.obj packet-adhctl.obj packet-adholsr.obj plugin.obj
>> >>> > ..\..\epan\libwiresh
>> >>> > ark.lib C:\wireshark-win32-libs\glib\lib\glib-2.0.lib
>> >>> > C:\wireshark-win32-libs\
>> >>> > glib\lib\gmodule-2.0.lib C:\wireshark-win32-libs\glib\lib\gobject-
>> >>> 2.0.lib
>> >>> > adh.r
> [snip]
> CONFIDENTIALITY NOTICE: The contents of this email are confidential
> and for the exclusive use of the intended recipient. If you receive this
> email in error, please delete it from your system immediately and
> notify us either by email, telephone or fax. You should not copy,
> forward, or otherwise disclose the content of the email.
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-dev
>
