History log of /freebsd-10.3-release/tools/regression/gaithrstress/gaithrstress.c
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
# 296373 04-Mar-2016 marius

- Copy stable/10@296371 to releng/10.3 in preparation for 10.3-RC1
builds.
- Update newvers.sh to reflect RC1.
- Update __FreeBSD_version to reflect 10.3.
- Update default pkg(8) configuration to use the quarterly branch.

Approved by: re (implicit)

# 282837 13-May-2015 ngie

MFC r282062:

Fix -Wformat warnings by using proper format string qualifiers for
long and unsigned[ long] types


# 256281 10-Oct-2013 gjb

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation


# 203800 12-Feb-2010 ru

Fixed error checking of pthread(3) functions.

PR: 143807
Submitted by: pluknet (partly)


# 126085 21-Feb-2004 green

Add some more comments and a -4 argument to restrict searches to only
A (not default A and AAAA) records. Now the longest time that a -4
thread might hang trying to resolve is only 2:30 instead of 5:00 ;)


# 126058 21-Feb-2004 green

Print the maximum resolution time encountered by each thread. Did you
know that the resolver might keep trying on a getaddrinfo() for up to
FIVE MINUTES?


# 126049 20-Feb-2004 green

Add my getaddrinfo(3) stress-tester as gaithrstress. The most obvious
regressions would be to see the program or your kernel crashing.

If you want to give it something to really test out, try a much more
reentrant version of the resolver.
<URL:http://green.homeunix.org/~green/reentrant_resolver.patch>
Any Mozilla-based browser would show you a clear difference.