[Wireshark-bugs] [Bug 16547] wireshark git master fails to build on GCC 9.3.1 ("error: ‘capture_file’ has not been declared")

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16547 Dario Lombardo changed: What|Removed |Added CC||lom...@gmail.com

[Wireshark-bugs] [Bug 15908] OpenVizsla/USB 2.0 Link-Layer capture dissection support

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15908 --- Comment #11 from Gerrit Code Review --- Change 37167 had a related patch set uploaded by Ameya Deshpande: USBLL: Reassembly of Control Transfers https://code.wireshark.org/review/37167 -- You are receiving this mail because: You

[Wireshark-bugs] [Bug 10503] TCP desegmentation does not handle a rollover of the TCP sequence number

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10503 --- Comment #20 from KH --- Created attachment 17754 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17754=edit Packet Trace: Only 4 selected frames causing Error 4 frames flagged by Expert Info. -- You are receiving this

[Wireshark-bugs] [Bug 10503] TCP desegmentation does not handle a rollover of the TCP sequence number

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10503 --- Comment #19 from KH --- Problem is still observed in recent 3.2.2. See attachment: https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17753 I can provide a packet trace file if required. (File is 240MB .pcap.gz) TCP sequence

[Wireshark-bugs] [Bug 10503] TCP desegmentation does not handle a rollover of the TCP sequence number

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10503 KH changed: What|Removed |Added CC||khnospam-wiresh...@yahoo.co

[Wireshark-bugs] [Bug 16335] PVS-Studio analyser long list of issues

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335 --- Comment #76 from Alexis La Goutte --- (In reply to Martin Mathieson from comment #75) > (In reply to Balling from comment #74) > > > https://www.transifex.com/wireshark/wireshark/, maybe send an email to > > > wireshark-dev mailing

[Wireshark-bugs] [Bug 16335] PVS-Studio analyser long list of issues

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335 --- Comment #75 from Martin Mathieson --- (In reply to Balling from comment #74) > > https://www.transifex.com/wireshark/wireshark/, maybe send an email to > > wireshark-dev mailing list? > > I signed up, but you need to allow me in the

[Wireshark-bugs] [Bug 16335] PVS-Studio analyser long list of issues

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335 --- Comment #74 from Balling --- > https://www.transifex.com/wireshark/wireshark/, maybe send an email to > wireshark-dev mailing list? I signed up, but you need to allow me in the group... -- You are receiving this mail because: You

[Wireshark-bugs] [Bug 16335] PVS-Studio analyser long list of issues

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335 --- Comment #73 from Martin Mathieson --- (In reply to Balling from comment #72) > > No, problem was that it delayed updating the offset after reading the PI > > But in that case that will be dead code! Now you do offset++ and everything

[Wireshark-bugs] [Bug 16335] PVS-Studio analyser long list of issues

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335 --- Comment #72 from Balling --- > No, problem was that it delayed updating the offset after reading the PI But in that case that will be dead code! Now you do offset++ and everything is good, I think. > Sadly, I couldn't find a spec for

[Wireshark-bugs] [Bug 16335] PVS-Studio analyser long list of issues

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335 --- Comment #71 from Martin Mathieson --- (In reply to Balling from comment #70) > An actual bug! > https://github.com/wireshark/wireshark/blob/ > 87f320ec25a27f06e90f68a200ab7702a5b7c850/epan/dissectors/packet-gsm_sms. > c#L2692 > This

[Wireshark-bugs] [Bug 16491] Packet List Pane doesn't consume the entire pane.

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16491 --- Comment #10 from Gerrit Code Review --- Change 37163 had a related patch set uploaded by Stig Bjørlykke: Qt: Respect user preference to hide packet list https://code.wireshark.org/review/37163 -- You are receiving this mail

[Wireshark-bugs] [Bug 16063] Deleting a column produces a crash

2020-05-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16063 --- Comment #15 from Gerrit Code Review --- Change 37163 had a related patch set uploaded by Stig Bjørlykke: Qt: Respect user preference to hide packet list https://code.wireshark.org/review/37163 -- You are receiving this mail