[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #14 from Gerrit Code Review  ---
Change 24848 merged by Michael Mann:
6LowPAN: always build IPv6 address whatever the tree state

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

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

Michael Mann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14266] In a WiFi capture log, the 11ac “beamformed” bit is shown as both “true” and “false”

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14266

--- Comment #15 from zpchi...@yahoo.com ---
I tested 2 scenarios:

In both scenario 1 and 2, TXOP_PS_NOT_ALLOWED should be True.

scenario 1: all packets are actually beamformed and in my sniffer capture I
observe that every packet shows:
a) Radiotap header v0 -> VHT info -> TXOP_PS_NOT_ALLOWED: True
b) Radiotap header v0 -> VHT info -> Beamformed: True
c) 802.11 radio info -> TXOP_PS_NOT_ALLOWED: False
d) 802.11 radio info -> Beamformed: False

So wireshark displays a) and b) correctly. c) and d) are wrong.

scenario 2: all packets are actually NOT beamformed and in my sniffer capture I
observe that every packet shows:
a) Radiotap header v0 -> VHT info -> TXOP_PS_NOT_ALLOWED: True
b) Radiotap header v0 -> VHT info -> Beamformed: False
c) 802.11 radio info -> TXOP_PS_NOT_ALLOWED: False
d) 802.11 radio info -> Beamformed: False

So wireshark displays a), b) and d) correctly. c) is wrong.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14229] Decoding ESP packets fails for similar IPs and the same SPI

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14229

--- Comment #2 from Gerrit Code Review  ---
Change 24469 merged by Michael Mann:
Rework address matching to work with string input.

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

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14229] Decoding ESP packets fails for similar IPs and the same SPI

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14229

Michael Mann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #13 from Gerrit Code Review  ---
Change 24848 had a related patch set uploaded by Pascal Quantin:
6LowPAN: always build IPv6 address whatever the tree state

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

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14276] New: Wireshark does not allow to copy "Decrypted SSL" text in non-tcp packet.

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14276

Bug ID: 14276
   Summary: Wireshark does not allow to copy "Decrypted SSL" text
in non-tcp packet.
   Product: Wireshark
   Version: 2.4.2
  Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Qt UI
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: mohe...@gmail.com
  Target Milestone: ---

Created attachment 16018
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16018=edit
There is no way to copy a text from the red frame

Build Information:
Version 2.4.2

Copyright 1998-2017 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.9.1, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with GLib 2.54.0, with zlib 1.2.11, without SMI, with c-ares
1.13.0, with Lua 5.2.4, with GnuTLS 3.5.15, with Gcrypt 1.8.1, with MIT
Kerberos, with GeoIP, with nghttp2 1.23.1, with LZ4, without Snappy, with
libxml2 2.9.5, with QtMultimedia, without AirPcap, without SBC, without
SpanDSP.

Running on Linux 4.13.12-1-ARCH, with Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
(with SSE4.2), with 7870 MB of physical memory, with locale en_US.UTF-8, with
libpcap version 1.8.1, with GnuTLS 3.5.16, with Gcrypt 1.8.1, with zlib 1.2.11.

Built using gcc 7.2.0.

Wireshark is Open Source Software released under the GNU General Public
License.
--
There is no way to copy a text from "Decrypted SSL" field as in the screenshot
if non-tcp packet is used.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14276] Wireshark does not allow to copy "Decrypted SSL" text in non-tcp packet.

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14276

mohe...@gmail.com changed:

   What|Removed |Added

  Attachment #16018|1   |0
is obsolete||

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14276] Wireshark does not allow to copy "Decrypted SSL" text in non-tcp packet.

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14276

mohe...@gmail.com changed:

   What|Removed |Added

  Attachment #16018|0   |1
is obsolete||
 CC||mohe...@gmail.com

--- Comment #1 from mohe...@gmail.com ---
Created attachment 16019
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16019=edit
pcap

SSL key logfile:

CLIENT_RANDOM 2F7DE3D9DAB8A81251460B903AFC4E7E689208B9B714DF9B7117806649F2653A
3ACC2F9EF3F927DCC7942B7C54E017E0D326EE2ACBB94B70F335F7FC49ECB50D8F809A04E25DF67356EB2661F00BC72B

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #6 from Mališa Vučinić  ---
(In reply to Guy Harris from comment #5)

> What happens if you run TShark with the -2 option, to force it to make two
> passes over the file?

Seg fault on the same line (packet-coap.c:864) :). Thanks, I can continue my
dissector development with one-pass tshark for now, but any help in tracking
this down would be appreciated.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

Pascal Quantin  changed:

   What|Removed |Added

 CC||pascal.quan...@gmail.com

--- Comment #7 from Pascal Quantin  ---
Do you have any local change that would register the CoAP dissector to a new
UDP port during runtime? Or any modification that would interact with CoAP?
As you seem to be working with 802.15.4 protocols, do you have a modification
that would prevent the 6lowpan or IPv6 dissector to be called on first pass?

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14266] In a WiFi capture log, the 11ac “beamformed” bit is shown as both “true” and “false”

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14266

--- Comment #13 from zpchi...@yahoo.com ---
seems so. I tested by saving 2 one-packet only files. Both show consistent
"true" beamformed 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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

Guy Harris  changed:

   What|Removed |Added

 Status|UNCONFIRMED |INCOMPLETE
 Ever confirmed|0   |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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #1 from Guy Harris  ---
(In reply to Mališa Vučinić from comment #0)
> Running on Mac OS X

...which means that there should be a crash report.  Launch Console and look
under "User Reports" for the crash report from Wireshark, and then either copy
the stack trace and paste it here, or attach the crash report file.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] New: Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

Bug ID: 14277
   Summary: Segmentation fault when opening a capture on Mac OS
build
   Product: Wireshark
   Version: 2.5.x (Experimental)
  Hardware: x86
OS: macOS 10.12
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Capture file support (libwiretap)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: malis...@gmail.com
  Target Milestone: ---

Created attachment 16020
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16020=edit
Capture that causes seg fault.

Build Information:
Compiled (64-bit) with Qt 5.10.0, with libpcap, without POSIX capabilities,
with
GLib 2.36.0, with zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua
5.2.4, without GnuTLS, with Gcrypt 1.7.7, with MIT Kerberos, with GeoIP,
without
nghttp2, with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with
SBC,
with SpanDSP, with bcg729.

Running on Mac OS X 10.12.6, build 16G1114 (Darwin 16.7.0), with   
Intel(R)
Core(TM) i7-3667U CPU @ 2.00GHz (with SSE4.2), with 8192 MB of physical memory,
with locale C, with libpcap version 1.8.1 -- Apple version 67.60.2, with Gcrypt
1.7.7, with zlib 1.2.8, binary plugins supported (0 loaded).

Built using clang 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2).
--
I have an issue with my Wireshark development build. I am currently on Version
2.5.0 (11a948dd). The build on Mac OS 10.12.6 completes without errors. When I
open the attached capture, I get “Segmentation fault: 11”. 

Behavior is consistent for other IEEE802.15.4 captures I have, but there are no
issues when I open a capture from
https://wiki.wireshark.org/SampleCaptures#DTLS_with_decryption_keys. A friend
has tried opening the attached file with the same revision, Linux build, and
had no troubles. Tshark on my machine dissects the attached file without
problems.  I also tried opening the attached file with 2.5.0-381-g36bc2c6,
binary downloaded from the website, and it worked. 

I tried building both with and without brew, using ./tools/macos-setup.sh and
./tools/macos-setup-brew.sh scripts. In both cases, the build would complete
but the seg fault behavior persisted.

Any hints would be appreciated.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13942] SIP Statistics extract does not work

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13942

Martin Mathieson  changed:

   What|Removed |Added

 CC||martin.r.mathieson@googlema
   ||il.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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14266] In a WiFi capture log, the 11ac “beamformed” bit is shown as both “true” and “false”

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14266

--- Comment #14 from Guy Harris  ---
(In reply to zpchi004 from comment #13)
> seems so. I tested by saving 2 one-packet only files. Both show consistent
> "true" beamformed information.

So are there packets near the offending packet that correctly display the
"beamformed" or TXOP_PS_NOT_ALLOWED values in the "802.11 radio" header, and
that have them both "false"?

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #4 from Mališa Vučinić  ---
Do you know what would cause p_get_proto_data() to fail with Wireshark but not
with tshark?

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14273] Add support for new Notify EMERGENCY_CALL_NUMBERS Payload in ISAKMP

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14273

--- Comment #2 from Gerrit Code Review  ---
Change 24793 merged by Anders Broman:
[ISAKMP] Added support for new Notify EMERGENCY_CALL_NUMBERS Payload

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

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #5 from Guy Harris  ---
(In reply to Mališa Vučinić from comment #4)
> Do you know what would cause p_get_proto_data() to fail with Wireshark but
> not with tshark?

TShark, by default, making only one pass over the packets, so that
PINFO_FD_VISITED(pinfo) is never true, and the per-packet information is
allocated?

What happens if you run TShark with the -2 option, to force it to make two
passes over the file?

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #2 from Mališa Vučinić  ---
Created attachment 16021
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16021=edit
Crash report.

Thanks for the quick reaction. Here is the crash report. I don't have any local
modifs.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

Guy Harris  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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #3 from Guy Harris  ---
Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x

Null-pointer dereference.

Stack trace:

0   libwireshark.0.dylib0x000106f72d3c dissect_coap + 156
(packet-coap.c:864)
1   libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
2   libwireshark.0.dylib0x000106d6585a dissector_try_uint +
106 (packet.c:1346)
3   libwireshark.0.dylib0x000107635697 decode_udp_ports +
583 (packet-udp.c:678)
4   libwireshark.0.dylib0x0001076370d3 dissect + 2787
(packet-udp.c:1139)
5   libwireshark.0.dylib0x000107636063 dissect_udp + 19
(packet-udp.c:1146)
6   libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
7   libwireshark.0.dylib0x000106d655cc
dissector_try_uint_new + 108 (packet.c:1346)
8   libwireshark.0.dylib0x0001071e8d7b ip_try_dissect + 139
(packet-ip.c:1857)
9   libwireshark.0.dylib0x00010720a6d7 ipv6_dissect_next +
295 (packet-ipv6.c:2462)
10  libwireshark.0.dylib0x00010720b627 dissect_ipv6 + 2503
(packet-ipv6.c:2412)
11  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
12  libwireshark.0.dylib0x000106d64812
call_dissector_with_data + 50 (packet.c:3071)
13  libwireshark.0.dylib0x000106ddec7c dissect_6lowpan +
3820
14  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
15  libwireshark.0.dylib0x000106d655cc
dissector_try_uint_new + 108 (packet.c:1346)
16  libwireshark.0.dylib0x0001071d4a31
dissect_ieee802154_common + 4593 (packet-ieee802154.c:1985)
17  libwireshark.0.dylib0x0001071d1c93 dissect_ieee802154 +
531 (packet-ieee802154.c:1212)
18  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
19  libwireshark.0.dylib0x000106d64812
call_dissector_with_data + 50 (packet.c:3071)
20  libwireshark.0.dylib0x00010775321f dissect_zep + 1295
21  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
22  libwireshark.0.dylib0x000106d6585a dissector_try_uint +
106 (packet.c:1346)
23  libwireshark.0.dylib0x0001076356ca decode_udp_ports +
634 (packet-udp.c:683)
24  libwireshark.0.dylib0x0001076370d3 dissect + 2787
(packet-udp.c:1139)
25  libwireshark.0.dylib0x000107636063 dissect_udp + 19
(packet-udp.c:1146)
26  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
27  libwireshark.0.dylib0x000106d655cc
dissector_try_uint_new + 108 (packet.c:1346)
28  libwireshark.0.dylib0x0001071e8d7b ip_try_dissect + 139
(packet-ip.c:1857)
29  libwireshark.0.dylib0x00010720a6d7 ipv6_dissect_next +
295 (packet-ipv6.c:2462)
30  libwireshark.0.dylib0x00010720b627 dissect_ipv6 + 2503
(packet-ipv6.c:2412)
31  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
32  libwireshark.0.dylib0x000106d6585a dissector_try_uint +
106 (packet.c:1346)
33  libwireshark.0.dylib0x0001070834de dissect_ethertype +
334 (packet-ethertype.c:271)
34  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
35  libwireshark.0.dylib0x000106d64812
call_dissector_with_data + 50 (packet.c:3071)
36  libwireshark.0.dylib0x000107082d3a dissect_eth_common +
3018 (packet-eth.c:539)
37  libwireshark.0.dylib0x00010708214b dissect_eth + 251
(packet-eth.c:802)
38  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
39  libwireshark.0.dylib0x000106d655cc
dissector_try_uint_new + 108 (packet.c:1346)
40  libwireshark.0.dylib0x0001070b410a dissect_frame + 4554
(packet-frame.c:563)
41  libwireshark.0.dylib0x000106d65729 call_dissector_work
+ 281 (packet.c:685)
42  libwireshark.0.dylib0x000106d64812
call_dissector_with_data + 50 (packet.c:3071)
43  libwireshark.0.dylib0x000106d646d5 dissect_record + 597
(packet.c:569)
44  libwireshark.0.dylib0x000106d5ab81 epan_dissect_run +
65 (epan.c:466)
45  org.wireshark.Wireshark 0x000105d8c650
PacketListRecord::dissect(_capture_file*, bool) + 464
(packet_list_record.cpp:194)
46  org.wireshark.Wireshark 0x000105d8c353

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

Guy Harris  changed:

   What|Removed |Added

  Component|Capture file support|Dissection engine
   |(libwiretap)|(libwireshark)

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

Guy Harris  changed:

   What|Removed |Added

   Hardware|x86 |x86-64

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #8 from Mališa Vučinić  ---
(In reply to Pascal Quantin from comment #7)
> Do you have any local change that would register the CoAP dissector to a new
> UDP port during runtime? Or any modification that would interact with CoAP?
> As you seem to be working with 802.15.4 protocols, do you have a
> modification that would prevent the 6lowpan or IPv6 dissector to be called
> on first pass?

No local changes whatsoever... I am on 11a948dd.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #11 from Mališa Vučinić  ---
In ~/.wireshark I have decode_as_entries with following content:

decode_as_entry: wpan.panid,43947,(none),6LoWPAN
decode_as_entry: wpan.panid,51966,(none),6LoWPAN

I also have entries for ieee802154_keys, dtlsdecrypttablefile and in
preferences smtp decryption is enabled, but that does not seem relevant for
this capture (no 802.15.4 security enabled, no dtls, no smtp traffic).

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #9 from Pascal Quantin  ---
Could you please share your preference file? Typically, what is your CoAP port
number configured? 5353? Something else?

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #10 from Pascal Quantin  ---
Based on your stack trace, you have the following dissectors chain:
IEEE802.15.4->6LoWPAN->IPv6->UDP->CoAP
while on my side for 6LoWPAN packets, I have
IEEE802.15.4->6LoWPAN->IPv6
So the difference is probably related to a preference setting.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build

2017-12-15 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277

--- Comment #12 from Mališa Vučinić  ---
No crash when I comment out decode_as_entries, but CoAP is not dissected
either.

-- 
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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe