Re: [Wireshark-dev] clang core dump on plugins/giop/packet-parlay.c

2011-04-22 Thread Stephen Fisher
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 bui

Re: [Wireshark-dev] clang core dump on plugins/giop/packet-parlay.c

2011-04-21 Thread Guy Harris
On Apr 21, 2011, at 12:35 PM, Sébastien Tandel wrote: > Hey Stephen! > > might be worth sharing with clang team, don't you think? A (non-public) bug has already been filed on it. > Have you tried to disable packet-parlay to check whether it is the only > dissector creating such an issue? It

Re: [Wireshark-dev] clang core dump on plugins/giop/packet-parlay.c

2011-04-21 Thread Sébastien Tandel
Hey Stephen! might be worth sharing with clang team, don't you think? Have you tried to disable packet-parlay to check whether it is the only dissector creating such an issue? Regards, Sebastien Tandel On Thu, Apr 21, 2011 at 16:30, Stephen Fisher wrote: > I'm trying again to get clang to com

[Wireshark-dev] clang core dump on plugins/giop/packet-parlay.c

2011-04-21 Thread Stephen Fisher
I'm trying again to get clang to compile Wireshark and after commenting out these two lines in configure.in temporarily: AC_WIRESHARK_GCC_CFLAGS_CHECK(-Wcast-align) AC_WIRESHARK_GCC_CFLAGS_CHECK(-fexcess-precision=fast) It gets all of the way to plugins/giop/packet-parlay.c and then clan