date:20170424

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

hhw  changed:

   What|Removed |Added

  Attachment #15501|0   |1
is obsolete||

--- Comment #16 from hhw  ---
Created attachment 15503
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15503&action=edit
scenario2 of sms 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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13658] New: Buildbot crash output: fuzz-2017-04-25-9297.pcap

2017-04-24 Thread bugzilla-daemon

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

Bug ID: 13658
   Summary: Buildbot crash output: fuzz-2017-04-25-9297.pcap
   Product: Wireshark
   Version: unspecified
  Hardware: x86-64
   URL: https://www.wireshark.org/download/automated/captures/
fuzz-2017-04-25-9297.pcap
OS: Ubuntu
Status: CONFIRMED
  Severity: Major
  Priority: High
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: buildbot-do-not-re...@wireshark.org
  Target Milestone: ---

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2017-04-25-9297.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/.cap

Build host information:
Linux wsbb04 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-build...@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=3998
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=dcaad43e1f65e8b99cbfed8b1b410e01eb1cad80

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit dcaad43e1f65e8b99cbfed8b1b410e01eb1cad80
Author: Pascal Quantin 
Date:   Mon Apr 24 22:52:52 2017 +0200

GSM SMS: add more lower layer info for reassembly and switch preference to
on by default

Change-Id: I3faf15c326d14e246975094ad31431eba2404d8c
Ping-Bug: 13592
Reviewed-on: https://code.wireshark.org/review/21320
Petri-Dish: Pascal Quantin 
Tested-by: Petri Dish Buildbot 
Reviewed-by: Pascal Quantin 


==9397== Memcheck, a memory error detector
==9397== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==9397== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==9397== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2017-04-25-9297.pcap
==9397== 
==9397== Invalid read of size 8
==9397==at 0x76DBEFB: wmem_list_foreach (wmem_list.c:267)
==9397==by 0x6B3F805: bootp_cleanup_protocol (packet-bootp.c:6343)
==9397==by 0xA40309C: g_slist_foreach (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==9397==by 0x6A0ABAA: cleanup_dissection (packet.c:343)
==9397==by 0x6A009BD: epan_free (epan.c:337)
==9397==by 0x414177: main (tshark.c:2113)
==9397==  Address 0x8 is not stack'd, malloc'd or (recently) free'd
==9397== 
==9397== 
==9397== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==9397==  Access not within mapped region at address 0x8
==9397==at 0x76DBEFB: wmem_list_foreach (wmem_list.c:267)
==9397==by 0x6B3F805: bootp_cleanup_protocol (packet-bootp.c:6343)
==9397==by 0xA40309C: g_slist_foreach (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==9397==by 0x6A0ABAA: cleanup_dissection (packet.c:343)
==9397==by 0x6A009BD: epan_free (epan.c:337)
==9397==by 0x414177: main (tshark.c:2113)
==9397==  If you believe this happened as a result of a stack
==9397==  overflow in your program's main thread (unlikely but
==9397==  possible), you can try to increase the size of the
==9397==  main thread stack using the --main-stacksize= flag.
==9397==  The main thread stack size used in this run was 2084864.
==9397== 
==9397== HEAP SUMMARY:
==9397== in use at exit: 25,770,114 bytes in 222,278 blocks
==9397==   total heap usage: 277,981 allocs, 55,703 frees, 37,827,395 bytes
allocated
==9397== 
==9397== LEAK SUMMARY:
==9397==definitely lost: 36 bytes in 2 blocks
==9397==indirectly lost: 72 bytes in 3 blocks
==9397==  possibly lost: 0 bytes in 0 blocks
==9397==still reachable: 25,552,703 bytes in 221,469 blocks
==9397== suppressed: 217,303 bytes in 804 blocks
==9397== Rerun with --leak-check=full to see details of leaked memory
==9397== 
==9397== For counts of detected and suppressed errors, rerun with: -v
==9397== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
./tools/valgrind-wireshark.sh: line 149:  9397 Segmentation fault  (core
dumped) $cmdline > /dev/null

[ no debug trace ]

-- 
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 13657] New: Reload this file button triggers segmentation fault

2017-04-24 Thread bugzilla-daemon

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

Bug ID: 13657
   Summary: Reload this file button triggers segmentation fault
   Product: Wireshark
   Version: Git
  Hardware: x86
OS: macOS 10.12
Status: UNCONFIRMED
  Severity: Normal
  Priority: Low
 Component: Qt UI
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: daniel.simio...@gmail.com
  Target Milestone: ---

Build Information:
Adrians-MacBook-Pro:wireshark asimionov$ wireshark -v
Wireshark 2.2.4 (v2.2.4-0-gcc3dc1b)

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.3.2, with libpcap, without POSIX capabilities, with
GLib 2.36.0, with zlib 1.2.5, with SMI 0.4.8, with c-ares 1.12.0, with Lua
5.2.4, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
with QtMultimedia, without AirPcap.

Running on Mac OS X 10.12.5, build 16F60a (Darwin 16.6.0), with locale
en_AU.UTF-8, with libpcap version 1.8.1 -- Apple version 67.60.1, with GnuTLS
2.12.19, with Gcrypt 1.5.0, with zlib 1.2.8.
Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Steps to reproduce:

open a pcap file
click "Reload this file" button

Result:
Segmentation fault: 11

-- 
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 13656] New: HEX highligh wrong byte

2017-04-24 Thread bugzilla-daemon

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

Bug ID: 13656
   Summary: HEX highligh wrong byte
   Product: Wireshark
   Version: Git
  Hardware: x86
OS: macOS 10.12
Status: UNCONFIRMED
  Severity: Minor
  Priority: Low
 Component: Qt UI
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: daniel.simio...@gmail.com
  Target Milestone: ---

Created attachment 15502
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15502&action=edit
issue of BYTE highlight

Build Information:
Adrians-MacBook-Pro:wireshark asimionov$ wireshark -v
Wireshark 2.2.4 (v2.2.4-0-gcc3dc1b)

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.3.2, with libpcap, without POSIX capabilities, with
GLib 2.36.0, with zlib 1.2.5, with SMI 0.4.8, with c-ares 1.12.0, with Lua
5.2.4, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
with QtMultimedia, without AirPcap.

Running on Mac OS X 10.12.5, build 16F60a (Darwin 16.6.0), with locale
en_AU.UTF-8, with libpcap version 1.8.1 -- Apple version 67.60.1, with GnuTLS
2.12.19, with Gcrypt 1.5.0, with zlib 1.2.8.
Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Please check the attached GIF. When I move the mouse, I would expect the yellow
BYTE to be the one mouse is over, but it seems there is a gap. More I move the
mouse, bigger the gap becomes.

-- 
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 13654] Buildbot crash output: fuzz-2017-04-24-6324.pcap

2017-04-24 Thread bugzilla-daemon

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

Pascal Quantin  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE
 CC||pascal.quan...@gmail.com

--- Comment #1 from Pascal Quantin  ---


*** This bug has been marked as a duplicate of bug 13655 ***

-- 
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 13655] After loading a capture file, Wireshark crashes upon exiting.

2017-04-24 Thread bugzilla-daemon

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

Pascal Quantin  changed:

   What|Removed |Added

 CC||buildbot-do-not-reply@wires
   ||hark.org

--- Comment #3 from Pascal Quantin  ---
*** Bug 13654 has been marked as a duplicate of this bug. ***

-- 
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 13655] After loading a capture file, Wireshark crashes upon exiting.

2017-04-24 Thread bugzilla-daemon

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

Alexis La Goutte  changed:

   What|Removed |Added

 CC||alexis.lagou...@gmail.com,
   ||mman...@netscape.net

-- 
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 13655] After loading a capture file, Wireshark crashes upon exiting.

2017-04-24 Thread bugzilla-daemon

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

--- Comment #2 from Guy Harris  ---
(In reply to Guy Harris from comment #1)
> Possibly a result of If52c00bbc23d89386ba3e777600f665609856de0.

Backing that change out seems to prevent the crash.

I'll look at trying with an ASAN build.

-- 
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 13655] After loading a capture file, Wireshark crashes upon exiting.

2017-04-24 Thread bugzilla-daemon

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

Guy Harris  changed:

   What|Removed |Added

   Hardware|x86-64  |All
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 OS|Windows 10  |All

--- Comment #1 from Guy Harris  ---
Confirmed on macOS with tip of master branch and a small capture with DHCP
traffic.  The stack trace is

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libwireshark.0.dylib0x00010aa24b40 wmem_list_foreach +
16 (wmem_list.c:267)
1   libwireshark.0.dylib0x000109e563f9
bootp_cleanup_protocol + 25 (packet-bootp.c:6345)
2   libglib-2.0.0.dylib 0x00010f44c49d g_slist_foreach + 45
(gslist.c:893)
3   libwireshark.0.dylib0x000109d1bbce cleanup_dissection +
30 (packet.c:346)
4   libwireshark.0.dylib0x000109d11253 epan_free + 19
(epan.c:339)
5   wireshark   0x00010937e113 cf_close + 451
(file.c:478)
6

...

Possibly a result of If52c00bbc23d89386ba3e777600f665609856de0.

-- 
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 13655] After loading a capture file, Wireshark crashes upon exiting.

2017-04-24 Thread bugzilla-daemon

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

Christopher Maynard  changed:

   What|Removed |Added

   Priority|Low |High

-- 
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 13655] New: After loading a capture file, Wireshark crashes upon exiting.

2017-04-24 Thread bugzilla-daemon

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

Bug ID: 13655
   Summary: After loading a capture file, Wireshark crashes upon
exiting.
   Product: Wireshark
   Version: Git
  Hardware: x86-64
OS: Windows 10
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: christopher.mayn...@igt.com
  Target Milestone: ---

Build Information:
Version 2.3.0 (v2.3.0rc0-3280-g13fbdfc)

Compiled (64-bit) with Qt 5.6.2, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0,
with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with AirPcap,
with
SBC, with SpanDSP.

Running on 64-bit Windows 10, build 10586, with Intel(R) Xeon(R) CPU E3-1505M
v5
@ 2.80GHz (with SSE4.2), with 16206 MB of physical memory, with locale
English_United States.1252, 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.4.11, with Gcrypt 1.7.6, with AirPcap 4.1.0 build 1622.

Built using Microsoft Visual C++ 12.0 build 31101
--
I tried with several capture files and Wireshark crashed after loading every
one and then exiting, so I think any capture file will do for testing purposes.
 Wireshark does not crash with Version 2.3.0 (v2.3.0rc0-3108-g74784bd).

Call Stack:

>   libwireshark.dll!wmem_list_foreach(_wmem_list_t * list, void (void *, 
> void *) * foreach_func, void * user_data) Line 267C
libwireshark.dll!bootp_cleanup_protocol() Line 6345 C
libglib-2.0-0.dll!6860d103()Unknown
libwireshark.dll!cleanup_dissection() Line 346  C
libwireshark.dll!epan_free(epan_session * session) Line 339 C
Wireshark.exe!cf_close(_capture_file * cf) Line 483 C
Wireshark.exe!MainWindow::testCaptureFileClose(QString before_what,
MainWindow::FileCloseContext context) Line 1807 C++
Wireshark.exe!MainWindow::closeEvent(QCloseEvent * event) Line 893 
C++
Qt5Widgets.dll!61771f87()   Unknown
Qt5Widgets.dll!61747d92()   Unknown
Qt5Widgets.dll!61746caf()   Unknown
Qt5Core.dll!6137fda9()  Unknown
Qt5Widgets.dll!6176ec59()   Unknown
Qt5Widgets.dll!61798f9e()   Unknown
Qt5Widgets.dll!61798660()   Unknown
Qt5Widgets.dll!61747d92()   Unknown
Qt5Widgets.dll!61746caf()   Unknown
Qt5Core.dll!6137fda9()  Unknown
Qt5Gui.dll!7fff90750804()   Unknown
Qt5Gui.dll!7fff90753f22()   Unknown
Qt5Gui.dll!7fff907383ac()   Unknown
Qt5Core.dll!613c7025()  Unknown
[External Code] 
Qt5Core.dll!613c6799()  Unknown
qwindows.dll!7fff9a3e31b9() Unknown
Qt5Core.dll!6137c6c1()  Unknown
Qt5Core.dll!6137eba7()  Unknown
Wireshark.exe!main(int argc, char * * qt_argv) Line 907 C++
[External Code]

-- 
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 13654] New: Buildbot crash output: fuzz-2017-04-24-6324.pcap

2017-04-24 Thread bugzilla-daemon

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

Bug ID: 13654
   Summary: Buildbot crash output: fuzz-2017-04-24-6324.pcap
   Product: Wireshark
   Version: unspecified
  Hardware: x86-64
   URL: https://www.wireshark.org/download/automated/captures/
fuzz-2017-04-24-6324.pcap
OS: Ubuntu
Status: CONFIRMED
  Severity: Major
  Priority: High
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: buildbot-do-not-re...@wireshark.org
  Target Milestone: ---

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2017-04-24-6324.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/.cap

Build host information:
Linux wsbb04 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-build...@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=3997
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=13fbdfc1ba9e38a45336f2d06e35083ba7da3d16

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 13fbdfc1ba9e38a45336f2d06e35083ba7da3d16
Author: Jakub Zawadzki 
Date:   Mon Apr 24 22:20:44 2017 +0200

fuzzshark: try to fix oss-build, remove oss-fuzzshark.c in old location.

Step #3: /src/wireshark/tools/oss-fuzzshark.c:190:2: warning: implicit
declaration of function 'wtap_init' is invalid in C99
[-Wimplicit-function-declaration]
   
(https://oss-fuzz-build-logs.storage.googleapis.com/log-472514ce-1a41-4f14-8798-d45084212a65.txt)

Change-Id: I47715bdf55c20124a80da51d3c8812db1d8d94cf
Reviewed-on: https://code.wireshark.org/review/21317
Reviewed-by: Jakub Zawadzki 
Petri-Dish: Jakub Zawadzki 
Tested-by: Petri Dish Buildbot 


==6387== Memcheck, a memory error detector
==6387== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==6387== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==6387== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2017-04-24-6324.pcap
==6387== 
==6387== Invalid read of size 8
==6387==at 0x76DBE5B: wmem_list_foreach (wmem_list.c:267)
==6387==by 0x6B3F805: bootp_cleanup_protocol (packet-bootp.c:6343)
==6387==by 0xA40309C: g_slist_foreach (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==6387==by 0x6A0ABAA: cleanup_dissection (packet.c:343)
==6387==by 0x6A009BD: epan_free (epan.c:337)
==6387==by 0x414177: main (tshark.c:2113)
==6387==  Address 0x8 is not stack'd, malloc'd or (recently) free'd
==6387== 
==6387== 
==6387== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==6387==  Access not within mapped region at address 0x8
==6387==at 0x76DBE5B: wmem_list_foreach (wmem_list.c:267)
==6387==by 0x6B3F805: bootp_cleanup_protocol (packet-bootp.c:6343)
==6387==by 0xA40309C: g_slist_foreach (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==6387==by 0x6A0ABAA: cleanup_dissection (packet.c:343)
==6387==by 0x6A009BD: epan_free (epan.c:337)
==6387==by 0x414177: main (tshark.c:2113)
==6387==  If you believe this happened as a result of a stack
==6387==  overflow in your program's main thread (unlikely but
==6387==  possible), you can try to increase the size of the
==6387==  main thread stack using the --main-stacksize= flag.
==6387==  The main thread stack size used in this run was 2084864.
==6387== 
==6387== HEAP SUMMARY:
==6387== in use at exit: 25,770,754 bytes in 222,296 blocks
==6387==   total heap usage: 277,997 allocs, 55,701 frees, 37,833,903 bytes
allocated
==6387== 
==6387== LEAK SUMMARY:
==6387==definitely lost: 36 bytes in 2 blocks
==6387==indirectly lost: 72 bytes in 3 blocks
==6387==  possibly lost: 0 bytes in 0 blocks
==6387==still reachable: 25,553,343 bytes in 221,487 blocks
==6387== suppressed: 217,303 bytes in 804 blocks
==6387== Rerun with --leak-check=full to see details of leaked memory
==6387== 
==6387== For counts of detected and suppressed errors, rerun with: -v
==6387== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
./tools/valgrind-wireshark.sh: line 149:  6387 Segmentation fault  (core
dumped) $cmdline > /dev/null

[ no debug trace ]

-- 
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
Unsubscr

[Wireshark-bugs] [Bug 13613] [oss-fuzz] UBSAN: shift exponent -3 is negative in proto.c:10593:38

2017-04-24 Thread bugzilla-daemon

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

--- Comment #5 from Jaap Keuter  ---
*** Bug 13640 has been marked as a duplicate of this bug. ***

-- 
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 13640] [oss-fuzz] UBSAN: shift exponent -3 is negative in proto.c:10593:38

2017-04-24 Thread bugzilla-daemon

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

Jaap Keuter  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Jaap Keuter  ---


*** This bug has been marked as a duplicate of bug 13613 ***

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #15 from Gerrit Code Review  ---
Change 21320 had a related patch set uploaded by Pascal Quantin:
GSM SMS: add more lower layer info for reassembly and switch preference to on
by default

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

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #14 from hhw  ---
(In reply to hhw from comment #11)
> More details are in attachments:scenario1.PNG, scenario2.PNG

in some cases  because of delay in network, segments are not submited /deliverd
Respectively

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #13 from hhw  ---
Created attachment 15501
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15501&action=edit
scenario2 of sms 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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #12 from hhw  ---
Created attachment 15500
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15500&action=edit
scenario1 of sms 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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #11 from hhw  ---
More details are in attachments:scenario1.PNG, scenario2.PNG

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #10 from Pascal Quantin  ---
(In reply to hhw from comment #9)
> in GSM_SMS over gsm_map-tcap We have 2 scenario:
> 
> Scenario 1: 
> Each part of sms submit/deliver in a Separate dialog(Transaction
> Capabilities Application Part), in this scenario each part has sm_RP_DA
> field that contain IMSI of DA/OA(gsm_old.sm_RP_DA==0), and all parts of a
> multipart sms have same  sm_RP_DA/OA. In other words, in this senario
> SM-RP-OA/DA field is always present and containing IMSI of DA/OA.
> 
> 
> 
> Scenario 2: 
> All parts of a multipart sms submit/deliver in one dialog, in this scenario
> one part should has sm_RP_DA/OA field that contain IMSI of
> DA/OA(gsm_old.sm_RP_DA==0)and in other parts sm_RP_DA/OA field is not always
> present(optionaly).in this Scenario parts that have same Source Transaction
> ID(otid) and same Destination Transaction ID(dtid)should be reassembled.

Thanks for the clarification.
This adds an extra layer of complexity that I will not manage for now. For
reference, a capture for scenario 2 can be found here:
https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6772

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #9 from hhw  ---
in GSM_SMS over gsm_map-tcap We have 2 scenario:

Scenario 1: 
Each part of sms submit/deliver in a Separate dialog(Transaction Capabilities
Application Part), in this scenario each part has sm_RP_DA field that contain
IMSI of DA/OA(gsm_old.sm_RP_DA==0), and all parts of a multipart sms have same 
sm_RP_DA/OA. In other words, in this senario SM-RP-OA/DA field is always
present and containing IMSI of DA/OA.



Scenario 2: 
All parts of a multipart sms submit/deliver in one dialog, in this scenario one
part should has sm_RP_DA/OA field that contain IMSI of
DA/OA(gsm_old.sm_RP_DA==0)and in other parts sm_RP_DA/OA field is not always
present(optionaly).in this Scenario parts that have same Source Transaction
ID(otid) and same Destination Transaction ID(dtid)should be reassembled.

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #8 from hhw  ---
(In reply to Pascal Quantin from comment #7)
> If you took a precompiled binary, this is normal as the patch was not merged
> yet.
> If you built yourself, then in GSM SMS dissector options you must activate
> the new setting asking to take into account lower layer info.

thanks,it is OK

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #7 from Pascal Quantin  ---
If you took a precompiled binary, this is normal as the patch was not merged
yet.
If you built yourself, then in GSM SMS dissector options you must activate the
new setting asking to take into account lower layer info.

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #6 from hhw  ---
(In reply to Pascal Quantin from comment #5)
> It means that you will have a GSM SMS dissector preference to toggle to
> activate the feature.
> It is off by default as I found some previous captures where the SM-RP-OA/DA
> field is not always present, breaking reassembly.

ok.but after new wireshark  build, in sample pcap(SMS_IMSI.pcap) packet 1 and 2
are parts of a 3 part SMS, but packet 3 has diffrent sm-RP-OA (IMSI) so it is
not part 3 of that SMS,however wireshark is reassembled them.

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #5 from Pascal Quantin  ---
It means that you will have a GSM SMS dissector preference to toggle to
activate the feature.
It is off by default as I found some previous captures where the SM-RP-OA/DA
field is not always present, breaking 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://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

2017-04-24 Thread bugzilla-daemon

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

--- Comment #4 from hhw  ---
(In reply to Gerrit Code Review from comment #3)
> Change 21306 had a related patch set uploaded by Pascal Quantin:
> GSM SMS: optionally use GSM-MAP info to perform reassembly (off by default)
> 
> https://code.wireshark.org/review/21306

thanks. what is the meaning of off by default? Whether I should change any
dissector to  use GSM-MAP info to perform reassembly by default?

-- 
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 13653] extcap: Several issues when capturing from multiple extcap interfaces

2017-04-24 Thread bugzilla-daemon

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

Stig Bjørlykke  changed:

   What|Removed |Added

 CC||rkn...@gmail.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 13653] New: extcap: Several issues when capturing from multiple extcap interfaces

2017-04-24 Thread bugzilla-daemon

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

Bug ID: 13653
   Summary: extcap: Several issues when capturing from multiple
extcap interfaces
   Product: Wireshark
   Version: 2.2.6
  Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
  Severity: Normal
  Priority: Low
 Component: Extras
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: s...@bjorlykke.org
  Target Milestone: ---

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Several issues when capturing from multiple extcap interfaces:

- extcap_create_pipe() does not create unique pipe name for each interface.
- extcap_if_cleanup() only closes one of the pipes because pipe_h is global.


This is Windows only.

-- 
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 13652] Import latest Ixia Veriwave code where appropriate

2017-04-24 Thread bugzilla-daemon

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

Alexis La Goutte  changed:

   What|Removed |Added

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

--- Comment #1 from Alexis La Goutte  ---
do you have try to apply on 2.2.1 and rebase ?

-- 
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 13652] New: Import latest Ixia Veriwave code where appropriate

2017-04-24 Thread bugzilla-daemon

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

Bug ID: 13652
   Summary: Import latest Ixia Veriwave code where appropriate
   Product: Wireshark
   Version: Git
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: Enhancement
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: jma...@loplof.de
  Target Milestone: ---

Created attachment 15499
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15499&action=edit
Diff to Wireshark Source 2.2.1

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Ixia updated their version of Wireshark last time for IxVeriwave 6.10.1 based
on Wireshark 2.2.1.
Attached is a diff between the original Wireshark 2.2.1 code and the Ixia 2.2.1
source code (currently seems to require a partner account to download).

This diff is a complete diff against 2.2.1. The idea is to check what is worth
adding to the standard code base and how.

-- 
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 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13658] New: Buildbot crash output: fuzz-2017-04-25-9297.pcap

[Wireshark-bugs] [Bug 13657] New: Reload this file button triggers segmentation fault

[Wireshark-bugs] [Bug 13656] New: HEX highligh wrong byte

[Wireshark-bugs] [Bug 13654] Buildbot crash output: fuzz-2017-04-24-6324.pcap

[Wireshark-bugs] [Bug 13655] After loading a capture file, Wireshark crashes upon exiting.

[Wireshark-bugs] [Bug 13655] After loading a capture file, Wireshark crashes upon exiting.

[Wireshark-bugs] [Bug 13655] After loading a capture file, Wireshark crashes upon exiting.

[Wireshark-bugs] [Bug 13655] After loading a capture file, Wireshark crashes upon exiting.

[Wireshark-bugs] [Bug 13655] After loading a capture file, Wireshark crashes upon exiting.

[Wireshark-bugs] [Bug 13655] New: After loading a capture file, Wireshark crashes upon exiting.

[Wireshark-bugs] [Bug 13654] New: Buildbot crash output: fuzz-2017-04-24-6324.pcap

[Wireshark-bugs] [Bug 13613] [oss-fuzz] UBSAN: shift exponent -3 is negative in proto.c:10593:38

[Wireshark-bugs] [Bug 13640] [oss-fuzz] UBSAN: shift exponent -3 is negative in proto.c:10593:38

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13592] GSM SMS dissector does not take into account lower layer info for reassembly

[Wireshark-bugs] [Bug 13653] extcap: Several issues when capturing from multiple extcap interfaces

[Wireshark-bugs] [Bug 13653] New: extcap: Several issues when capturing from multiple extcap interfaces

[Wireshark-bugs] [Bug 13652] Import latest Ixia Veriwave code where appropriate

[Wireshark-bugs] [Bug 13652] New: Import latest Ixia Veriwave code where appropriate

30 matches

Site Navigation

Mail list logo

Footer information