Wireshark-dev: Re: [Wireshark-dev] Custom Plugin Protocol not showing in new version
From: <champhastings@xxxxxxxxxxxxx>
Date: Wed, 18 Jul 2007 15:47:42 -0400
This is working now. I did not copy over the correct .dll. (I'm not very smart sometimes) So recompiling with the new sources did work. Thank you again. Chad > > From: <champhastings@xxxxxxxxxxxxx> > Date: 2007/07/18 Wed PM 03:37:22 EDT > To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx> > Subject: Re: [Wireshark-dev] Custom Plugin Protocol > not showing in new version > > I recompiled the plugin with the new sources and I'm still getting the same thing. It only shows UDP in the Protocol column. It still dissects fine, so I know at least part of the plugin is working. Any more help would be appreciated. > > > > From: <champhastings@xxxxxxxxxxxxx> > > Date: 2007/07/18 Wed AM 10:24:49 EDT > > To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx> > > Subject: Re: [Wireshark-dev] Custom Plugin Protocol not > > showing in new version > > > > I have not try recompiling yet. I will. Thank you for your reply. > > > > > > From: Guy Harris <guy@xxxxxxxxxxxx> > > > Date: 2007/07/17 Tue PM 06:22:38 EDT > > > To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx> > > > Subject: Re: [Wireshark-dev] Custom Plugin Protocol not showing > > > in new version > > > > > > > > > On Jul 17, 2007, at 3:18 PM, Stephen Fisher wrote: > > > > On Tue, Jul 17, 2007 at 03:09:11PM -0500, Chad Hastings wrote: > > > > > > > >> I have a custom protocol plugin that was working fine in 99.5, but in > > > >> 99.6 the protocol column does not show the correct name. It only > > > >> shows > > > >> UDP or TCP where as before it had my custom name (AAA and BBB not > > > >> that > > > >> it matters). It still dissects fine, and the filter works, but the > > > >> protocol column is wrong. Anyone else having this trouble? > > > > > > > > Did you recompile your plug-in with 0.99.6 sources? > > > ...and re-install it in the 0.99.6 directory? Currently, the ABIs for > > > plugins are *NOT* stable, and may change from release to release, so > > > 1) plugins are searched for in a directory containing the version > > > numbers, so that plugins built and installed for versions other than > > > the running version are *not* seen (i.e., that's by design and intent); > > > 2) you have to recompile your plugin with every release. > > > _______________________________________________ > > > 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 >
- Prev by Date: Re: [Wireshark-dev] Custom Plugin Protocol not showing in new version
- Next by Date: [Wireshark-dev] RFC 4411 and 4412
- Previous by thread: Re: [Wireshark-dev] Custom Plugin Protocol not showing in new version
- Next by thread: [Wireshark-dev] RFC 4411 and 4412
- Index(es):