Skip to content
Snippets Groups Projects
New look: Off

Buildbot crash output: fuzz-2015-03-25-30531.pcap

    • Closed Issue created by Wireshark GitLab Migration @ws-gitlab-migration

    This issue was migrated from bug 11088 in our old bug tracker.

    Original bug information:

    Reporter: Buildbot Builder
    Status: RESOLVED FIXED
    Product: Wireshark
    Component: Dissection engine (libwireshark)
    OS: Ubuntu
    Platform: x86-64
    Version: unspecified

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

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Buildbot Builder said:

      Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2015-03-25-30531.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/test-io-graph

Build host information:
Linux wsbb04 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.2 LTS
Release:	14.04
Codename:	trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=3192
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=a6fc6aa0b4efc1a1c3d7a2e3b5189e888fb6ccc2

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit a6fc6aa0b4efc1a1c3d7a2e3b5189e888fb6ccc2
Author: Evan Huus <eapache@gmail.com>
Date:   Sat Mar 21 13:19:25 2015 -0400

    wcp: add validations to decompressed_entry

    Ensure that a reference to past bytes refers to bytes that actually exist.

    Bug: 10978
    Change-Id: If95d785ee15243c88edcd7115b5ff25fbaa08e6c
    Reviewed-on: https://code.wireshark.org/review/7783
    Petri-Dish: Evan Huus <eapache@gmail.com>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Evan Huus <eapache@gmail.com>


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

==7921== Memcheck, a memory error detector
==7921== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==7921== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==7921== Command: /home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark -nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2015-03-25-30531.pcap
==7921==
==7921==
==7921== HEAP SUMMARY:
==7921==     in use at exit: 2,678,380 bytes in 53,738 blocks
==7921==   total heap usage: 4,183,842 allocs, 4,130,104 frees, 236,947,329 bytes allocated
==7921==
==7921== LEAK SUMMARY:
==7921==    definitely lost: 135,800 bytes in 2,221 blocks
==7921==    indirectly lost: 171,832 bytes in 2,952 blocks
==7921==      possibly lost: 0 bytes in 0 blocks
==7921==    still reachable: 2,370,748 bytes in 48,565 blocks
==7921==         suppressed: 0 bytes in 0 blocks
==7921== Rerun with --leak-check=full to see details of leaked memory
==7921==
==7921== For counts of detected and suppressed errors, rerun with: -v
==7921== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)

[ no debug trace ]
    • Wireshark GitLab Migration added crash libwireshark osubuntu labels

      added crash libwireshark osubuntu labels

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Evan Huus said:

      ==20851== 22,448 (10,736 direct, 11,712 indirect) bytes in 122 blocks are definitely lost in loss record 3,555 of 3,564
==20851==    at 0x4C2ABA0: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20851==    by 0xB8AC7C9: g_malloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB8C370F: g_slice_alloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB89577D: g_hash_table_new_full (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0x75692CE: x11_stateinit (packet-x11.c:4805)
==20851==    by 0x75EA4E7: dissect_x11_replies (packet-x11.c:4845)
==20851==    by 0x6A98D49: call_dissector_through_handle (packet.c:614)
==20851==    by 0x6A99F40: call_dissector_work (packet.c:700)
==20851==    by 0x6A9ABB2: dissector_try_uint_new (packet.c:1132)
==20851==    by 0x743B546: decode_tcp_ports (packet-tcp.c:4129)
==20851==    by 0x743BAF4: process_tcp_payload (packet-tcp.c:4187)
==20851==    by 0x743C3F7: dissect_tcp_payload (packet-tcp.c:4262)
==20851==
==20851== 22,448 (10,736 direct, 11,712 indirect) bytes in 122 blocks are definitely lost in loss record 3,556 of 3,564
==20851==    at 0x4C2ABA0: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20851==    by 0xB8AC7C9: g_malloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB8C370F: g_slice_alloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB89577D: g_hash_table_new_full (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0x75692E9: x11_stateinit (packet-x11.c:4806)
==20851==    by 0x75EA4E7: dissect_x11_replies (packet-x11.c:4845)
==20851==    by 0x6A98D49: call_dissector_through_handle (packet.c:614)
==20851==    by 0x6A99F40: call_dissector_work (packet.c:700)
==20851==    by 0x6A9ABB2: dissector_try_uint_new (packet.c:1132)
==20851==    by 0x743B546: decode_tcp_ports (packet-tcp.c:4129)
==20851==    by 0x743BAF4: process_tcp_payload (packet-tcp.c:4187)
==20851==    by 0x743C3F7: dissect_tcp_payload (packet-tcp.c:4262)
==20851==
==20851== 27,600 (13,200 direct, 14,400 indirect) bytes in 150 blocks are definitely lost in loss record 3,559 of 3,564
==20851==    at 0x4C2ABA0: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20851==    by 0xB8AC7C9: g_malloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB8C370F: g_slice_alloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB89577D: g_hash_table_new_full (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0x75692CE: x11_stateinit (packet-x11.c:4805)
==20851==    by 0x75EEB97: dissect_x11_requests (packet-x11.c:4550)
==20851==    by 0x6A98D49: call_dissector_through_handle (packet.c:614)
==20851==    by 0x6A99F40: call_dissector_work (packet.c:700)
==20851==    by 0x6A9ABB2: dissector_try_uint_new (packet.c:1132)
==20851==    by 0x743B5BF: decode_tcp_ports (packet-tcp.c:4134)
==20851==    by 0x743BAF4: process_tcp_payload (packet-tcp.c:4187)
==20851==    by 0x743C3F7: dissect_tcp_payload (packet-tcp.c:4262)
==20851==
==20851== 27,600 (13,200 direct, 14,400 indirect) bytes in 150 blocks are definitely lost in loss record 3,560 of 3,564
==20851==    at 0x4C2ABA0: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20851==    by 0xB8AC7C9: g_malloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB8C370F: g_slice_alloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB89577D: g_hash_table_new_full (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0x75692E9: x11_stateinit (packet-x11.c:4806)
==20851==    by 0x75EEB97: dissect_x11_requests (packet-x11.c:4550)
==20851==    by 0x6A98D49: call_dissector_through_handle (packet.c:614)
==20851==    by 0x6A99F40: call_dissector_work (packet.c:700)
==20851==    by 0x6A9ABB2: dissector_try_uint_new (packet.c:1132)
==20851==    by 0x743B5BF: decode_tcp_ports (packet-tcp.c:4134)
==20851==    by 0x743BAF4: process_tcp_payload (packet-tcp.c:4187)
==20851==    by 0x743C3F7: dissect_tcp_payload (packet-tcp.c:4262)
==20851==
==20851== 64,768 (30,976 direct, 33,792 indirect) bytes in 352 blocks are definitely lost in loss record 3,563 of 3,564
==20851==    at 0x4C2ABA0: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20851==    by 0xB8AC7C9: g_malloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB8C370F: g_slice_alloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB89577D: g_hash_table_new_full (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0x75692CE: x11_stateinit (packet-x11.c:4805)
==20851==    by 0x75EEB97: dissect_x11_requests (packet-x11.c:4550)
==20851==    by 0x6A98D49: call_dissector_through_handle (packet.c:614)
==20851==    by 0x6A99F40: call_dissector_work (packet.c:700)
==20851==    by 0x6A9ABB2: dissector_try_uint_new (packet.c:1132)
==20851==    by 0x743B546: decode_tcp_ports (packet-tcp.c:4129)
==20851==    by 0x743BAF4: process_tcp_payload (packet-tcp.c:4187)
==20851==    by 0x743C3F7: dissect_tcp_payload (packet-tcp.c:4262)
==20851==
==20851== 64,768 (30,976 direct, 33,792 indirect) bytes in 352 blocks are definitely lost in loss record 3,564 of 3,564
==20851==    at 0x4C2ABA0: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20851==    by 0xB8AC7C9: g_malloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB8C370F: g_slice_alloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0xB89577D: g_hash_table_new_full (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1)
==20851==    by 0x75692E9: x11_stateinit (packet-x11.c:4806)
==20851==    by 0x75EEB97: dissect_x11_requests (packet-x11.c:4550)
==20851==    by 0x6A98D49: call_dissector_through_handle (packet.c:614)
==20851==    by 0x6A99F40: call_dissector_work (packet.c:700)
==20851==    by 0x6A9ABB2: dissector_try_uint_new (packet.c:1132)
==20851==    by 0x743B546: decode_tcp_ports (packet-tcp.c:4129)
==20851==    by 0x743BAF4: process_tcp_payload (packet-tcp.c:4187)
==20851==    by 0x743C3F7: dissect_tcp_payload (packet-tcp.c:4262)
    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Gerrit Code Review said:

      Change 7835 had a related patch set uploaded by Evan Huus: x11: destroy two more hash tables in convo data

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

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Gerrit Code Review said:

      Change 7835 merged by Evan Huus: x11: destroy two more hash tables in convo data

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

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Gerrit Code Review said:

      Change 7838 had a related patch set uploaded by Evan Huus: x11: destroy two more hash tables in convo data

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

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Gerrit Code Review said:

      Change 7839 had a related patch set uploaded by Evan Huus: x11: destroy two more hash tables in convo data

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

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Gerrit Code Review said:

      Change 7838 merged by Evan Huus: x11: destroy two more hash tables in convo data

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

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Gerrit Code Review said:

      Change 7839 merged by Evan Huus: x11: destroy two more hash tables in convo data

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

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Gerrit Code Review said:

      Change 8637 had a related patch set uploaded by Balint Reczey: x11: destroy two more hash tables in convo data

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

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Gerrit Code Review said:

      Change 8637 merged by Balint Reczey: x11: destroy two more hash tables in convo data

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

    • Wireshark GitLab Migration closed

      closed

    Please register or sign in to reply