Wireshark mailing list archives
Re: clang core dump on plugins/giop/packet-parlay.c
From: Stephen Fisher <steve () stephen-fisher com>
Date: Fri, 22 Apr 2011 14:11:38 -0600
On Thu, Apr 21, 2011 at 12:46:08PM -0700, Guy Harris wrote:
Have you tried to disable packet-parlay to check whether it is the only dissector creating such an issue?It takes about 2GB or more of memory in the static analyzer to analyze dissect_parlay(); is the static analyzer built 64-bit or 32-bit, or is it running out of swap space+memory?
I didn't check before uninstalling and installing clang 3.0 from trunk (svn r129935), which successfully compiles this. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- clang core dump on plugins/giop/packet-parlay.c Stephen Fisher (Apr 21)
- Re: clang core dump on plugins/giop/packet-parlay.c Sébastien Tandel (Apr 21)
- Re: clang core dump on plugins/giop/packet-parlay.c Guy Harris (Apr 21)
- Re: clang core dump on plugins/giop/packet-parlay.c Stephen Fisher (Apr 22)
- Re: clang core dump on plugins/giop/packet-parlay.c Guy Harris (Apr 21)
- Re: clang core dump on plugins/giop/packet-parlay.c Sébastien Tandel (Apr 21)