https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16245
Bug ID: 16245
Summary: Crash after closing the Edit Column widget
Product: Wireshark
Version: Git
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: Qt UI
Assignee: bugzilla-ad...@wireshark.org
Reporter: jyo...@gsu.edu
Target Milestone: ---
Build Information:
Wireshark 3.3.0rc0-58-g890e2bea2ef2 (v3.3.0rc0-58-g890e2bea2ef2)
Copyright 1998-2019 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<https://www.gnu.org/licenses/gpl-2.0.html>
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.12.5, with libpcap, without POSIX capabilities,
with
GLib 2.37.6, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.15.0, with Lua
5.2.4, with GnuTLS 3.4.17, with Gcrypt 1.7.7, with MIT Kerberos, with MaxMind
DB
resolver, with nghttp2 1.39.2, with brotli, with LZ4, with Zstandard, with
Snappy, with libxml2 2.9.9, with QtMultimedia, with SpeexDSP (using bundled
resampler), with SBC, with SpanDSP, with bcg729.
Running on Mac OS X 10.13.6, build 17G9016 (Darwin 17.7.0), with Intel(R)
Core(TM) i7-4870HQ CPU @ 2.50GHz (with SSE4.2), with 16384 MB of physical
memory, with locale en_US.UTF-8, with libpcap version 1.8.1 -- Apple version
79.20.1, with GnuTLS 3.4.17, with Gcrypt 1.7.7, with brotli 1.0.7, with zlib
1.2.11, binary plugins supported (0 loaded).
Built using clang 4.2.1 Compatible Apple LLVM 11.0.0 (clang-1100.0.33.8).
--
A crash can be triggered when closing the Packet List's header context menu's
Edit Column widget. This appears to happen when there is already is at least
one custom column defined for the current profile.
Starting with a new default profile (no custom columns).
1 Right click on one of the standard (non-custom) column Header names (for
example "Source") to open the context menu and select the "Edit Column" item.
2 In the column editor click in the "Fields:" text entry and type some trivial
display filter such as "ip" or "frame" (any valid filter name will do).
3 Accept and close the Edit Column widget.
4 Click on another non-custom column Header (for example "Destination") to
again open the context menu and again select the "Edit Column" item.
5 As was done in step 2 click on the "Fields:" entry and again enter some
trivial display like "ip".
6 Accept and close the Edit column widget.
7 Crash.
Problem first seen when working with a recent buildbot generated Development
version on macOS.
> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
> Exception Note: EXC_CORPSE_NOTIFY
>
> Termination Signal: Segmentation fault: 11
> Termination Reason: Namespace SIGNAL, Code 0xb
> Terminating Process: exc handler [0]
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 libsystem_platform.dylib 0x00007fff755a4750 _platform_strcmp +
> 176
> 1 wireshark 0x000000010ae4657b
> recent_get_column_width + 107 (recent.c:1458)
> 2 wireshark 0x000000010aad5396
> ColumnEditorFrame::on_buttonBox_accepted() + 246
> 3 wireshark 0x000000010aad56ab
> ColumnEditorFrame::keyPressEvent(QKeyEvent*) + 107
<snip>
Duplicated using recent buildbot generated Development version on Windows.
With the appropriate PDB files and source it provided this:
> Wireshark.exe!recent_get_column_width(int col) Line 1458
> Wireshark.exe!ColumnEditorFrame::on_buttonBox_accepted() Line 145
> Wireshark.exe!ColumnEditorFrame::keyPressEvent(QKeyEvent * event) Line 169
<snip>
Which pointed to this line of code in ui/recent.s's recent_get_column_width():
> if (cfmt != COL_CUSTOM || strcmp (cfield, col_w->cfield) == 0) {
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
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
