[Wireshark-bugs] [Bug 12522] Double escaping of backslash in Regex required

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12522

--- Comment #5 from Thomas W.  ---
It does not seem consistent to me in that online tester:
Regex: @@ V\?
Input: @@ D1
Outcome (in column labelled $var = $input =~ $regex): $var is a null string
This indicates to me that there is no match.

> What if you try: xml matches "\"@@ V\"?"
The \" at the beginning could be 
- an escaped quotation mark
- a backslash + a quotation mark
The \"? at the end could be
- an optional escaped quotation mark
- a backslash + an optional quotation mark

Perhaps you have hit the source of the problem: if a backslash is needed to
escape the quotation mark, then there needs to be a way of escaping the
backslash as well (\\).

If that is the case, I guess only option 2 is left:
> Expected behavior, option 2 (not preferred): a single backslash results in an 
> invalid Regex, indicated by a red background in the display filter box. When 
> using double backslashes, the display filter background becomes green.

Then, the documentation at https://wiki.wireshark.org/DisplayFilters should be
updated to make it clear that Wireshark does not use "clean" Regex but escaped
ones.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 9014] crashes with option "-z io, stat, ..." in the presence of negative relative packet timestamps

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9014

--- Comment #10 from Gerrit Code Review  ---
Change 16046 had a related patch set uploaded by Michael Mann:
Check for negative nanoseconds in io,stat tap.

https://code.wireshark.org/review/16046

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12548] Add support for defragmentation of PPP Multilink (RFC 1990) and its multiclass extension (RFC 2686)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12548

Alexis La Goutte  changed:

   What|Removed |Added

 CC||alexis.lagou...@gmail.com

--- Comment #2 from Alexis La Goutte  ---
Can you attach a pcap ?

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12548] Add support for defragmentation of PPP Multilink (RFC 1990) and its multiclass extension (RFC 2686)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12548

Michael Mann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
  Component|Documentation   |Dissection engine
   ||(libwireshark)
 Ever confirmed|0   |1
   Severity|Major   |Enhancement

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12288] Wireshark crashes every time open Statistics -> Conversations | Endpoints

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12288

Luiz Felipe Lins Dias  changed:

   What|Removed |Added

   Priority|Low |Medium
 Status|UNCONFIRMED |CONFIRMED
 CC||floki...@gmail.com
   Hardware|x86 |x86-64
   Target Milestone|--- |2.0 release
 Ever confirmed|0   |1
 OS|Mac OS X 10.11  |Windows 7

--- Comment #1 from Luiz Felipe Lins Dias  ---
The same problem occurs to me.

Files above a certain size about 200 MegaBytes, when going on statistics menu
and select endpoints or Conversations, after a certain amount processed the GUI
freezes and wire-shark crash.



Copyright 1998-2016 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
Intel(R) Core(TM) i5 CPU 650  @ 3.20GHz (with SSE4.2), with 8054MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 40629

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.



Faulting application name: Wireshark.exe, version: 2.0.3.0, time stamp:
0x571a5d95
Faulting module name: Wireshark.exe, version: 2.0.3.0, time stamp: 0x571a5d95
Exception code: 0xc005
Fault offset: 0x00055b71
Faulting process id: 0x3430
Faulting application start time: 0x01d1cb27dec4de70
Faulting application path: C:\Program Files\Wireshark\Wireshark.exe
Faulting module path: C:\Program Files\Wireshark\Wireshark.exe
Report Id: 19e1d6ab-3728-11e6-8a83-001a7dda7113

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12547] editcap -r stops writing packets at the end of the first selection or range

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12547

--- Comment #1 from Gerrit Code Review  ---
Change 16045 had a related patch set uploaded by John Thacker:
Editcap: Fix setting of max_packet_number

https://code.wireshark.org/review/16045

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12548] Add support for defragmentation of PPP Multilink (RFC 1990) and its multiclass extension (RFC 2686)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12548

--- Comment #1 from Gerrit Code Review  ---
Change 16044 had a related patch set uploaded by John Thacker:
PPP MP: Support reassembly of PPP MP (RFC 1990) and Multi-class (RFC 2686)

https://code.wireshark.org/review/16044

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12548] New: Add support for defragmentation of PPP Multilink (RFC 1990) and its multiclass extension (RFC 2686)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12548

Bug ID: 12548
   Summary: Add support for defragmentation of PPP Multilink (RFC
1990) and its multiclass extension (RFC 2686)
   Product: Wireshark
   Version: Git
  Hardware: x86
OS: All
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Documentation
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: johnthac...@gmail.com

Build Information:
Wireshark 2.1.1-git (v2.1.1rc0-187-g2dc3e52 from unknown)

Copyright 1998-2016 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.8.8, with Pango 1.28.1, with
libpcap, without POSIX capabilities, with libnl 3, with GLib 2.28.8, with zlib
1.2.3, without SMI, with c-ares 1.10.0, with Lua 5.1, without GnuTLS, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Jul
 8 2010), without AirPcap.

Running on Linux 2.6.32-573.22.1.el6.x86_64, with locale en_US.UTF-8, with
libpcap version 1.4.0, with Gcrypt 1.4.5, with zlib 1.2.3.
   Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz (with SSE4.2)

Built using gcc 4.4.7 20120313 (Red Hat 4.4.7-17).

--
Add support for RFC 2686, The Multi-class Extension to Multilink PPP, and add
support for defragmenting PPP Multilink (RFC 1990) whether it has RFC 2686
multiclass or not.

The multi-class part is fairly easy, as it just uses some of the previously
reserved bits (and the new bits are used to distinguish otherwise identical
sequence numbers.)

The reassembly is trickier, since the other sequence based dissectors expect a
sequence number for the reassembled packet plus a fragment number within the
reassembly. PPP Multilink provides a single sequence number that is effectively
the sum of those two, plus flags that indicate whether a fragment is the first
or last member of a reassembly. This leads to a bit of guessing until we get
enough packets to finish a reassembly.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12547] New: editcap -r stops writing packets at the end of the first selection or range

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12547

Bug ID: 12547
   Summary: editcap -r stops writing packets at the end of the
first selection or range
   Product: Wireshark
   Version: Git
  Hardware: x86
OS: All
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Extras
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: johnthac...@gmail.com

Created attachment 14670
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14670&action=edit
Patch to fix.

Build Information:
TShark (Wireshark) 2.1.1-git (v2.1.1rc0-187-g2dc3e52 from unknown)

Copyright 1998-2016 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with libpcap, without POSIX capabilities, with libnl 3, with
GLib 2.28.8, with zlib 1.2.3, without SMI, with c-ares 1.10.0, with Lua 5.1,
without GnuTLS, with Gcrypt 1.4.5, with MIT Kerberos, with GeoIP.

Running on Linux 2.6.32-573.22.1.el6.x86_64, with locale en_US.UTF-8, with
libpcap version 1.4.0, with Gcrypt 1.4.5, with zlib 1.2.3.
   Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz (with SSE4.2)

Built using gcc 4.4.7 20120313 (Red Hat 4.4.7-17).
--
The change in bug 9686 is broken. The test for setting max_packet_number
(max_selection in add_selected) is wrong, and is set to the maximum packet
number in the first selection or range given on the command line.

Expected behavior:
./editcap -v -r in.pcap out.pcap 1 50 100
File /home/johnthac/m0_zte_capture.pcap is a Wireshark/tcpdump/... - pcap
capture file.
Add_Selected: 1
Not inclusive ... 1
Add_Selected: 50
Not inclusive ... 50
Add_Selected: 100
Not inclusive ... 100
Packet: 1
Packet: 50
Packet: 100

Actual behavior:
./editcap -v -r int.pcap out.pcap 1 50 100
File /home/johnthac/m0_zte_capture.pcap is a Wireshark/tcpdump/... - pcap
capture file.
Add_Selected: 1
Not inclusive ... 1
Add_Selected: 50
Not inclusive ... 50
Add_Selected: 100
Not inclusive ... 100
Packet: 1

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12522] Double escaping of backslash in Regex required

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12522

Christopher Maynard  changed:

   What|Removed |Added

 Status|INCOMPLETE  |CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12522] Double escaping of backslash in Regex required

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12522

--- Comment #4 from Christopher Maynard  ---
(In reply to Thomas W. from comment #2)
> Created attachment 14668 [details]
> Capture to proof that wrong results are found
> 
> Regex: xml matches "@@ V\?"
> Finds (guess): @@ D1
> Potential cause (guess): V is considered as optional as in V?
> 
> Regex: xml matches "@@ V\\?"
> Finds nothing (as expected)

I'm certainly no Perl expert, but the behavior *seems* consistent with the
online Perl regex tester: http://www.regexplanet.com/advanced/perl/index.html.

What if you try: xml matches "\"@@ V\"?"

(In reply to Thomas W. from comment #3)
> Created attachment 14669 [details]
> Capture to play with double escaping of \
> 
> Regex: xml matches "@@ V1\\*"
> Expected: no results, since there is no backslash in the XML
> Actual Result: @@ V1* is found

No results are found if xml matches "\"@@ V1\"*" is applied.  It looks like
an additional level of escaping is required.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12208] RFC5515 not supported

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12208

--- Comment #14 from jewgenij.bytsch...@t-systems.com ---
Yes, the fix works with Wireshark 2.1.0 development release. I have installed
this version and successfully checked RFC5515 related functionality with it.
Thank you for the provided solution!

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12067] Unable to resize the packet list pane, packet details pane

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12067

--- Comment #7 from James Elliott  ---
I feel your pain! Sadly I am buried in side-projects which are what are pulling
me into Wireshark in the first place, for reverse-engineering synchronization
protocols used by DJ equipment, so I very much don’t have time to try to learn
the Wireshark and QT internals and help with this.

I can report, however, that removing it and reinstalling it --with-qt-5 made
everything work fine, so I am going to remove my votes, and just use the newer
QT version!

Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12208] RFC5515 not supported

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12208

--- Comment #12 from Anders Broman  ---
New functionallity is not backported, these enhancments will be available in 
2.2.x. On Window you can use a development build until next version is
released.

https://www.wireshark.org/download/automated/ 

Regards
Anders

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12208] RFC5515 not supported

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12208

--- Comment #13 from Pascal Quantin  ---
The fix is part of the Wireshark 2.1.x branch, not 2.0.x one.
I guess you should have it if you install Wireshark 2.1.0 development release,
found on www.wireshark.org download page.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12208] RFC5515 not supported

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12208

--- Comment #11 from jewgenij.bytsch...@t-systems.com ---
The fix (Bug 12208) is not available in or does not work with the new Wireshark
2.0.4. All the RFC5515 AVP types are 'unknown' again and the AVP values are not
displayed in readable form in Wireshark 2.0.4.

You can check this after download the pcap traces (two attachments) provided in
this ticket earlier.

Verified with:
Version 2.0.4 (v2.0.4-0-gdd7746e from master-2.0)

Copyright 1998-2016 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
AMD E1-1200 APU with Radeon(tm) HD Graphics, with 3689MB of physical memory.


Built using Microsoft Visual C++ 12.0 build 40629

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11754] Add JSON as an output format

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11754

--- Comment #15 from Gerrit Code Review  ---
Change 16037 had a related patch set uploaded by Dario Lombardo:
json: sanitize json output format.

https://code.wireshark.org/review/16037

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11754] Add JSON as an output format

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11754

--- Comment #14 from Dario Lombardo  ---
Current json output is invalid. I'll push a change for the errors, but there
are still some warnings to get rid of.

https://jsonformatter.curiousconcept.com/

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11754] Add JSON as an output format

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11754

--- Comment #13 from Gerrit Code Review  ---
Change 16034 had a related patch set uploaded by Martin Kacer:
tshark JSON and Elasticsearch output fix

https://code.wireshark.org/review/16034

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12522] Double escaping of backslash in Regex required

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12522

--- Comment #3 from Thomas W.  ---
Created attachment 14669
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14669&action=edit
Capture to play with double escaping of \

Regex: xml matches "@@ V1\\*"
Expected: no results, since there is no backslash in the XML
Actual Result: @@ V1* is found

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12522] Double escaping of backslash in Regex required

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12522

--- Comment #2 from Thomas W.  ---
Created attachment 14668
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14668&action=edit
Capture to proof that wrong results are found

Regex: xml matches "@@ V\?"
Finds (guess): @@ D1
Potential cause (guess): V is considered as optional as in V?

Regex: xml matches "@@ V\\?"
Finds nothing (as expected)

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe