Re: [Wireshark-dev] Custom display formatting for FT_STRING

Have you looked into using proto_tree_add_string() and friends, such as proto_tree_add_string_format() and proto_tree_add_string_format_value()? - Chris > -Original Message- > From: Wireshark-dev On Behalf > Of Bernhard Dick > Sent: Thursday, November 24, 2022 11:03 AM > To: wireshark-de

Re: [Wireshark-dev] can't compile wireshark version 4.0

FYI: Guy Harris provided a fix, originally with https://gitlab.com/wireshark/wireshark/-/commit/de50666ec077a0b09f3d61ccd20870a03db52c92 but then more simply with https://gitlab.com/wireshark/wireshark/-/commit/de50666ec077a0b09f3d61ccd20870a03db52c92. - Chris From: Wireshark-dev On Behalf Of

Re: [Wireshark-dev] can't compile wireshark version 4.0

I suppose it's complaining about this test as always evaluating to false: ba[i] < '\0' What if you simply remove that part, does it compile then? - Chris From: Wireshark-dev On Behalf Of w...@comcast.net Sent: Wednesday, October 19, 2022 10:17 AM To: wireshark-dev@wireshark.org; w...@comcast.n

Re: [Wireshark-dev] On building better statistics

> -Original Message- > From: Wireshark-dev On Behalf > Of João Valverde > Sent: Monday, February 14, 2022 10:34 AM > To: Developer support list for Wireshark ; > Jaap Keuter > Subject: Re: [Wireshark-dev] On building better statistics > > I don't typically use Protocol Hierarchy statistic

Re: [Wireshark-dev] Swap 'v'|'V' options for editcap and mergecap

It would be nice if they were all documented too. See also: https://gitlab.com/wireshark/wireshark/-/issues/15483. - Chris > -Original Message- > From: Wireshark-dev On Behalf > Of Gerald Combs > Sent: Monday, October 18, 2021 9:48 PM > To: Developer support list for Wireshark ; > chuck

Re: [Wireshark-dev] WSDG: "foo" protocol sample capture

I don't know if there's ever been a companion capture file to test the sample "Foo" dissector or not, so I created one. I also created a comparable "Foo" dissector written in Lua to complement the C dissector for those who are just getting started with Lua. The Lua dissector contains many lin

Re: [Wireshark-dev] Enhancement suggestion: OUI tool for IPV6 SLAAC addresses

> -Original Message- > From: Wireshark-dev On Behalf > Of Maynard, Christopher via Wireshark-dev > Sent: Monday, August 2, 2021 9:13 PM > To: 'Developer support list for Wireshark' > Cc: Maynard, Christopher > Subject: Re: [Wireshark-dev] Enhancemen

Re: [Wireshark-dev] Enhancement suggestion: OUI tool for IPV6 SLAAC addresses

- Chris > -Original Message- > From: Wireshark-dev On Behalf > Of João Valverde via Wireshark-dev > Sent: Friday, July 30, 2021 10:20 AM > To: wireshark-dev@wireshark.org > Cc: João Valverde > Subject: Re: [Wireshark-dev] Enhancement suggestion: OUI tool for IPV6 > SLAAC addresses > >

Re: [Wireshark-dev] warning LNK4291: module may contain '__except' but was not compiled with /guard:ehcont

> From: Wireshark-dev On Behalf Of Graham > Bloice > Sent: Friday, July 2, 2021 11:53 AM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] warning LNK4291: module may contain '__except' > but was not compiled with /guard:ehcont > > I'd be interested to know if you see li

Re: [Wireshark-dev] warning LNK4291: module may contain '__except' but was not compiled with /guard:ehcont

i Chris, > > 2 juil. 2021 17:36:21 Maynard, Christopher via Wireshark-dev > <mailto:wireshark-dev@wireshark.org>: > >> I’m not sure if these warnings have been seen by anyone yet, but I just >> noticed them after updating sources today and compiling. >> &g

[Wireshark-dev] warning LNK4291: module may contain '__except' but was not compiled with /guard:ehcont

I'm not sure if these warnings have been seen by anyone yet, but I just noticed them after updating sources today and compiling. From: https://gitlab.com/wireshark/wireshark/-/jobs/1395187730#L534 libmaxminddb.lib(maxminddb.c.obj) : warning LNK4291: module may contain '__except' (Structured Exce

Re: [Wireshark-dev] Struggling to rebase

> From: Wireshark-dev On Behalf Of chuck c > Sent: Friday, March 5, 2021 5:26 PM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Struggling to rebase > > But sometimes I'm this guy: > https://twitter.com/catalinmpit/status/1301965170076459009 Naturally, there's a releva

[Wireshark-dev] Lua stringz

Hi list, I was successfully using tvbrange:stringz() to retrieve a NULL-terminated string from a tvb, that is until I recently encountered a string containing extended-ASCII characters, at which point things starting failing because the length of the string returned was too long. To work aroun

Re: [Wireshark-dev] Documentation : 9.6. How to produce protocol stats merge request

> From: Wireshark-dev On Behalf Of Graham > Bloice > Sent: Thursday, December 24, 2020 6:10 AM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Documentation : 9.6. How to produce protocol > stats merge request > >> On Thu, 24 Dec 2020 at 10:49, wsgd

Re: [Wireshark-dev] Recent console warning from Qt?

> -Original Message- > From: Wireshark-dev On Behalf Of > Maynard, Christopher via Wireshark-dev > Sent: den 8 december 2020 16:20 > To: 'Developer support list for Wireshark' > Cc: Maynard, Christopher > Subject: Re: [Wireshark-dev] Recent console w

Re: [Wireshark-dev] Recent console warning from Qt?

> From: Wireshark-dev On Behalf Of Anders > Broman via Wireshark-dev > Sent: Tuesday, December 8, 2020 3:55 AM > To: wireshark-dev@wireshark.org > Cc: Anders Broman > Subject: [Wireshark-dev] Recent console warning from Qt? > > Hi, > Has anyone else seen this Main Warn QWinTaskbarButton: qIID_IT

Re: [Wireshark-dev] osqa-ask search - backend process?

> From: Wireshark-dev On Behalf Of chuck c > Sent: Sunday, November 29, 2020 10:57 PM > To: Developer support list for Wireshark > Subject: [Wireshark-dev] osqa-ask search - backend process? > > Should question search still work on the old Q&A site? > Tags and users searches return results. As I

[Wireshark-dev] Packet Diagram shows only raw bytes of a subtree instead of individual fields

Many protocols contain subtrees, such as a header with various fields that are part of the header, and it's convenient/logical to group those fields within the header subtree. However, doing so results in a Packet Diagram that only shows the raw bytes of the subtree rather than the individual f

Re: [Wireshark-dev] Qt warning on Windows build.

> From: Wireshark-dev On Behalf Of Anders > Broman via Wireshark-dev > Sent: Thursday, November 19, 2020 3:50 AM > To: wireshark-dev@wireshark.org > Cc: Anders Broman > Subject: [Wireshark-dev] Qt warning on Windows build. > > Hi, > Currently there is one Warnimg produced for the Windows build >