And https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11149 is potentially the same issue for 1.12 although it seems to have only happened the once.
On Sat, May 30, 2015 at 10:27 PM, Evan Huus <[email protected]> wrote: > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11147 and its many > duplicates suggest a similar issue with the master buildbot. > > On Sat, May 30, 2015 at 10:22 PM, Jeff Morriss > <[email protected]> wrote: >> There have been plenty of fuzz failures from the 1.10 branch in the past few >> months, including: >> >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11050 >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11065 >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11077 >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11090 >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11094 >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11150 >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11239 >> >> All of the captures associated with those bugs run fine for me. The last >> one's error: >> >>> >>> /home/wireshark/builders/wireshark-1.10-fuzz/fuzztest/build/.libs/lt-tshark: >>> error while loading shared libraries: libwireshark.so.3: failed to map >>> segment from shared object: Cannot allocate memory >> >> >> really supports the theory that it's not the software that has the problem >> but the buildbot itself. >> >> Is there something wrong with the box? >> >> In the mean time I'll close all those bugs as WORKSFORME. >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <[email protected]> >> Archives: https://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: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
