[Wireshark-bugs] [Bug 12580] (Qt5) after obtaining a packet trace, crashes when quitting or starting new trace

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12580

Alexis La Goutte  changed:

   What|Removed |Added

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

--- Comment #4 from Alexis La Goutte  ---
Thanks for the analysis and the patch 


Can you push the patch on Gerrit ?

-- 
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 12582] (Qt5) app menus won't pull down

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582

--- Comment #1 from Gerald Combs  ---
(In reply to Matt Day from comment #0)
> 2. start Wireshark

Are you doing this by running the Wireshark executable directory or by opening
its application bundle (assuming that homebrew creates an application bundle)?

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

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12067

--- Comment #11 from Gerald Combs  ---
(In reply to Matt Day from comment #8)
> It seems nobody has tested Wireshark+Qt5 much beyond successful compilation.

Are you referring to the official packages from wireshark.org or the
homebrew-compiled executables?

-- 
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 12580] (Qt5) after obtaining a packet trace, crashes when quitting or starting new trace

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12580

--- Comment #5 from Gerald Combs  ---
@Matt can you try the change in https://code.wireshark.org/review/#/c/16062/ ?

-- 
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 12583] New: Buildbot crash output: fuzz-2016-07-02-14934.pcap

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12583

Bug ID: 12583
   Summary: Buildbot crash output: fuzz-2016-07-02-14934.pcap
   Product: Wireshark
   Version: unspecified
  Hardware: x86-64
   URL: https://www.wireshark.org/download/automated/captures/
fuzz-2016-07-02-14934.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

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2016-07-02-14934.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/14696-sample.pcap

Build host information:
Linux wsbb04 3.13.0-86-generic #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:Ubuntu
Description:Ubuntu 14.04.4 LTS
Release:14.04
Codename:trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-build...@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=145
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.0/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=0fcd23ccac07a7f971ae7466808968bf642320af

Return value:  136

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 0fcd23ccac07a7f971ae7466808968bf642320af
Author: Matt Texier 
Date:   Wed Jun 29 17:33:21 2016 +0200

BGP dissector: Fixing NLRI length for flow spec NLRI

Bug: 12568
Change-Id: Id2b89c2d133865771e21acf3ee224f57ac9d262b
Reviewed-on: https://code.wireshark.org/review/16203
Reviewed-by: Alexis La Goutte 
(cherry picked from commit e55eaf573b593d9578aac6847acf3d79e5f3a7dc)
Reviewed-on: https://code.wireshark.org/review/16219
Petri-Dish: Alexis La Goutte 
Tested-by: Petri Dish Buildbot 
Reviewed-by: Jaap Keuter 


Command and args: ./tools/valgrind-wireshark.sh 

==10316== Memcheck, a memory error detector
==10316== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==10316== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==10316== Command:
/home/wireshark/builders/wireshark-2.0-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.0/fuzz-2016-07-02-14934.pcap
==10316== 
==10316== 
==10316== Process terminating with default action of signal 8 (SIGFPE): dumping
core
==10316==  Integer divide by zero at address 0x80435483C
==10316==at 0x6DE537D: dissect_pbb_tlvblock (packet-packetbb.c:289)
==10316==by 0x6DE55F0: dissect_pbb_header (packet-packetbb.c:686)
==10316==by 0x6DE55F0: dissect_packetbb (packet-packetbb.c:729)
==10316==by 0x684826E: call_dissector_through_handle (packet.c:618)
==10316==by 0x6848C04: call_dissector_work (packet.c:706)
==10316==by 0x68493FB: dissector_try_uint_new (packet.c:1163)
==10316==by 0x6849446: dissector_try_uint (packet.c:1189)
==10316==by 0x6FCAB79: decode_udp_ports (packet-udp.c:531)
==10316==by 0x6FCB46C: dissect (packet-udp.c:1003)
==10316==by 0x6848233: call_dissector_through_handle (packet.c:620)
==10316==by 0x6848C04: call_dissector_work (packet.c:706)
==10316==by 0x68493FB: dissector_try_uint_new (packet.c:1163)
==10316==by 0x6C2225D: ip_try_dissect (packet-ip.c:2000)
==10316== 
==10316== HEAP SUMMARY:
==10316== in use at exit: 18,223,049 bytes in 188,121 blocks
==10316==   total heap usage: 239,398 allocs, 51,277 frees, 31,128,789 bytes
allocated
==10316== 
==10316== LEAK SUMMARY:
==10316==definitely lost: 251 bytes in 17 blocks
==10316==indirectly lost: 0 bytes in 0 blocks
==10316==  possibly lost: 0 bytes in 0 blocks
==10316==still reachable: 18,222,798 bytes in 188,104 blocks
==10316== suppressed: 0 bytes in 0 blocks
==10316== Rerun with --leak-check=full to see details of leaked memory
==10316== 
==10316== For counts of detected and suppressed errors, rerun with: -v
==10316== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
./tools/valgrind-wireshark.sh: line 113: 10316 Floating point exception(core
dumped) $LIBTOOL valgrind --suppressions=`dirname $0`/vg-suppressions
--tool=$TOOL $CALLGRIND_OUT_FILE $VERBOSE $LEAK_CHECK $REACHABLE $TRACK_ORIGINS
$COMMAND $COMMAND_ARGS $PCAP $COMMAND_ARGS2 > /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://wireshark.org/mailman/options/wireshark-bugs

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

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12067

Alexis La Goutte  changed:

   What|Removed |Added

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

--- Comment #10 from Alexis La Goutte  ---
(In reply to Matt Day from comment #8)
> (In reply to James Elliott from comment #7)
> > 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!
> 
> I'm surprised to hear you say everything works fine with Qt 5, though I
> agree that at least the packet list panes are resizeable there.
> 
> When I built with Qt 5 to get resizeable packet list panes, I immediately
> ran into two new bugs:
> 
> bug 12580 - (Qt5) after obtaining a packet trace, crashes when quitting or
> starting new trace
> 
> bug 12582 - (Qt5) app menus won't pull down
> 
> It seems nobody has tested Wireshark+Qt5 much beyond successful compilation.

Hi Matt,
Do you have try with release from Wireshark.org ? May be a issue with Qt from
homebrew...

-- 
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 12581] ICMP Echo reply for ICMP Echo request to multicast address can't be found

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12581

João Valverde  changed:

   What|Removed |Added

   Severity|Normal  |Enhancement

--- Comment #3 from João Valverde  ---
The "no response found" message should be fixed on the master branch
(v2.1.1rc0), leaving this open in case someone wants to enhance ICMP echo reply
tracking for multicast requests (not working on it at the moment).

-- 
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 12579] TCP: nextseq incorrect if TCP_MAX_UNACKED_SEGMENTS exceeded & FIN true

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12579

--- Comment #1 from Jaap Keuter  ---
Created attachment 14702
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14702=edit
Generated capture from command line magic

This capture file, generated as listed in the report, would demonstrate the
issue.

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

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12067

--- Comment #12 from Gerald Combs  ---
(In reply to Gerald Combs from comment #11)
> (In reply to Matt Day from comment #8)
> > It seems nobody has tested Wireshark+Qt5 much beyond successful compilation.
> 
> Are you referring to the official packages from wireshark.org or the
> homebrew-compiled executables?

Note that I'm not trying to be snarky here. The official Wireshark packages for
macOS are compiled with versions of Qt, GLib, and other libraries that don't
change very often and are known to work reasonably well. The Wireshark
application is installed as an application bundle and *not* as a bare
executable. The further homebrew diverges from the wireshark.org installer the
more opportunities for misadventure will arise.

At the very least I think it'd be helpful if
https://github.com/Homebrew/homebrew-core/blob/master/Formula/wireshark.rb were
modified such that

- It installs Wireshark as Wireshark.app if it doesn't already do so. 
- It uses --with-qt and --with-qt4 instead of --with-qt5 and --with-qt to
install with Qt5 and Qt4 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://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12552] Wireshark dissects T.38 ECM image data as HDLC

2016-07-03 Thread bugzilla-daemon 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12552

Anish Bhatt  changed:

   What|Removed |Added

 CC||an...@gatech.edu

--- Comment #1 from Anish Bhatt  ---
Got a link to the spec that defines this ?

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