Hi Chris, >From the top of my head there's an environment variable which can be set on >running glib based apps that cause these apps to stop when they hit these. >Running in a debugger allows you to to backtrace to the source.
Thanks, Jaap Send from my iPhone On 2 okt. 2010, at 21:39, Chris Maynard <[email protected]> wrote: > Stephen Fisher <st...@...> writes: >> Do you have a different version installed on the system while you're >> trying to run from the build directory? I've run into problems in the >> past with that. >> > > Yes, an older version was already installed, 1.0.5. I removed it and did some > minor cleanup and was then able to run tshark from the build directory. > Before > I removed it, libtool showed the libraries linked as those in /usr/local/lib/ > rather than in <build_dir>/.libs/, so that definitely was the problem, > although > I find it a bit strange that it works during the build process (with 1.4.0 at > least) without having to uninstall the older version. That happens when > "tshark > -G" is run to generate wireshark-filter.pod, as in: > > WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 ../tshark -G fields | \ > /usr/bin/perl ./dfilter2pod.pl ./wireshark-filter.pod.template > > wireshark-filter.pod > > Anyway, thanks for your help on this one. One problem solved. Now to try to > figure out why I'm getting 23145 occurrences of the following GLib error when > I > try to run tshark: > > (process:19019): GLib-CRITICAL **: g_string_insert_c: assertion `pos <= > string-> > len' failed > > I've been seeing these errors for a long time now on this system (which is why > it was still running 1.0.5), but I hadn't dug deep enough yet to try to figure > out why and how to eliminate them. Any ideas on tracking this one down too > would be greatly appreciated. Is it possibly a glib version problem? This > system is running with glib2-2.12.3-2.fc6. I can't seem to find where the > minimum glib version requirement for wireshark is mentioned. > > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:[email protected]?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
