Great, thanks for the feedback!
One of my first tasks will be to support llvm/clang builds. I've seen some
prior discussion on what's needed for that, but if you have any extra tips
I'll take them. I'll be sure to create a build target for the fuzzers so
they can be run standalone.
Berkeley
On
Hi -
> There is of course some i/o delay involved. But the majority of the
> time is cpu bound because the file needs to be decompressed.
> Not that it would help us now, but I wonder if it would be worth it to
> look at parallel compression/decompression to speed things up.
Yeah, maybe.
> pick
Hi Berkeley,
On Fri, 2019-12-20 at 17:21 +0200, Berkeley Churchill wrote:
> Any interest in integrating with oss-fuzz? It's a google project
> that supports open source projects by fuzzing. It allows Google to
> find and report bugs, especially security bugs, to the project.
> I'm willing to work
Hi Frank,
On Wed, 2019-12-18 at 19:47 -0500, Frank Ch. Eigler wrote:
> [...]
> > I would add something like:
> >
> > /* Make sure there is at least some progress,
> > try to get at least 1K per progress timeout seconds. */
> > curl_easy_setopt(curl, CURLOPT_LOW_SPEED_TIME, 5 * 1024L);
>
Hi Frank,
On Fri, 2019-12-13 at 14:25 -0500, Frank Ch. Eigler wrote:
> > I see, I missed that both functions are only called after first
> > checking the archive type. I think it might be helpful/clearer if
> > both methods would be called with the intended archive type then,
> > also because that
