Wireshark-dev: Re: [Wireshark-dev] Unresolved call_dissector_only issue
From: Sean <yunjnz@xxxxxxxxx>
Date: Fri, 20 Mar 2009 10:23:10 -0700 (PDT)
I have another suggestion regarding this issue, Do you have any plan on exporting function req_resp_hdrs_do_reassembly? It seems that sometimes the plugins want to call this interface. --- On Mon, 3/16/09, Maynard, Chris <Christopher.Maynard@xxxxxxxxx> wrote: > From: Maynard, Chris <Christopher.Maynard@xxxxxxxxx> > Subject: Re: [Wireshark-dev] Unresolved call_dissector_only issue > To: "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx> > Date: Monday, March 16, 2009, 1:20 AM > > > > > > > > > > > > > > > > > epan/libwireshark.def did not include call_dissector_only in > 1.0.4. > > > > > > > > > > > > From: > wireshark-dev-bounces@xxxxxxxxxxxxx > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf > Of philippe > alarcon > > Sent: Sunday, March 15, 2009 12:04 PM > > To: wireshark-dev > > Subject: Re: [Wireshark-dev] Unresolved > call_dissector_only issue > > > > > > > > Hi Sean, > > > > Have you include packet.h file ? > > > > #include <epan/packet.h> > > > > Regards > > Philippe > > > > > > > > > Date: Sun, 15 Mar 2009 06:23:03 -0700 > > > From: yunjnz@xxxxxxxxx > > > To: wireshark-dev@xxxxxxxxxxxxx > > > Subject: [Wireshark-dev] Unresolved > call_dissector_only issue > > > > > > > > > Hi, > > > > > > I'm working on an external dissector, and I want > to call another dissector > from my dissector, > > > but when I use the function call_dissector_only, > > > the compiler complains: > > > error LNK2019: unresolved external symbol > _call_dissector_only referenced > in function _dissect_mydissector > > > > > > BTW, I'm working on version 1.0.4 and want to > compile the dissector as a > DLL. > > > Any clues on it? > > > Thanks a lot, > > > Sean > > > > > > > > > > > > > ___________________________________________________________________________ > > > Sent via: Wireshark-dev mailing list > <wireshark-dev@xxxxxxxxxxxxx> > > > Archives: > http://www.wireshark.org/lists/wireshark-dev > > > Unsubscribe: > https://wireshark.org/mailman/options/wireshark-dev > > > > mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe > > > > > > > > > Souhaitez > vous « être au bureau sans y > être » ? Oui > je le veux ! > > > > > > 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. > > > > > -----Inline Attachment Follows----- > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > > mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
- Follow-Ups:
- Re: [Wireshark-dev] Unresolved call_dissector_only issue
- From: Maynard, Chris
- Re: [Wireshark-dev] Unresolved call_dissector_only issue
- Prev by Date: Re: [Wireshark-dev] Help on NBAP
- Next by Date: Re: [Wireshark-dev] g_snprintf() and sizeof
- Previous by thread: Re: [Wireshark-dev] Unresolved call_dissector_only issue
- Next by thread: Re: [Wireshark-dev] Unresolved call_dissector_only issue
- Index(es):