Re: buildbot failure in Wireshark (development) on Ubuntu-10.04-x64

[Jaap Keuter <jaap.keuter () xs4all nl>]

Ok,

Go sit in the penalty box for 20 CPU cycles.

;)
Jaap

On 10/20/2010 07:57 PM, Hadriel Kaplan wrote:
> Yeah but I feel stupid because I actually found and fixed that bug in my local ipfix.c afterwards, and didn't go fix 
> it in the bug-database entry. :(
> -hadriel
>
> On Oct 20, 2010, at 12:28 PM, Bill Meier wrote:
>
> > Hadriel Kaplan wrote:
> > > Ugh - my patch submitted as bug 5242 caused it.  Sorry bout that.
> > > I didn't realize the bug was taken in yet (I had added myself to
> > > its cc list,  but never got an email).
> > >
> > > -hadriel
> >
> > Not a problem:
> >
> > It turns out that the addition of ipfix.c to wiretap exposed a bug in
> > another wiretap reader (ascendtext.c)
> > as well as the bug in ipfix.c that Jeff identified.
> >
> > (ascendtext.c wasn't properly initializing *err before using it thus
> > depending on whatever value *err had from previously invoked wiretap
> > readers).
> >
> > I'll be committing fixes shortly.
> >
> > Bill

___________________________________________________________________________
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