[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277 --- Comment #15 from Mališa Vučinić--- Thank you guys, just tested locally. This was amazingly quick! -- 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
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277 Michael Mannchanged: 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 14277] Segmentation fault when opening a capture on Mac OS build
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 14277] Segmentation fault when opening a capture on Mac OS build
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
[Wireshark-bugs] [Bug 14277] Segmentation fault when opening a capture on Mac OS build
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
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
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
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277 Pascal Quantinchanged: 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 14277] Segmentation fault when opening a capture on Mac OS build
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
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
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 14277] Segmentation fault when opening a capture on Mac OS build
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277 Guy Harrischanged: 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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277 Guy Harrischanged: 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
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277 Guy Harrischanged: 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
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14277 Guy Harrischanged: 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
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