Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • wireshark wireshark
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,337
    • Issues 1,337
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 150
    • Merge requests 150
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Wireshark Foundation
  • wiresharkwireshark
  • Issues
  • #17762
Closed
Open
Created Dec 02, 2021 by Joel Colledge@JoelColledgeContributor

Wireshark crashes if a 64 bit field of type BASE_CUSTOM is applied as a column

Summary

Wireshark crashes with

Unhandled exception ("field drbd.nodes_to_reach is a 64-bit field with a 32-bit value_string", group=1, code=6)
Aborted (core dumped)

when the field drbd.nodes_to_reach is applied as a column.

Steps to reproduce

  1. Open P_TWOPC_PREPARE.pcap with wireshark
  2. Expand the DRBD packet tree
  3. Right click the nodes_to_reach field and "Apply as column"

What is the current bug behavior?

Wireshark crashes.

What is the expected correct behavior?

A column is added with the nodes_to_reach value.

Sample capture file

P_TWOPC_PREPARE.pcap

Build information

Current master fe9b1fb1.

Analysis

My initial assumption was that the issue is in the DRBD dissector. However, there are other dissectors with FT_UINT64, BASE_CUSTOM, so this seems to be a valid combination.

Simply removing the REPORT_DISSECTOR_BUG from hf_try_val64_to_str fixes the issue. I don't know the wireshark internals well enough to judge whether this is an acceptable fix. See https://gitlab.com/wireshark/wireshark/-/blob/fe9b1fb103c1a4ec14b952e36e86915d6d14097e/epan/proto.c#L9467

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking