[OpenAFS] Collection User-Mode Application Dumps on Microsoft Windows Vista, Win7 and Server 2008 [R2]

Jeffrey Altman jaltman@your-file-system.com
Mon, 12 Dec 2011 13:15:29 -0500


This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig62EA4D9FE26043F57EF78560
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body bgcolor=3D"#ffffff" text=3D"#000000">
    <tt>If you have the OpenAFS Windows 1.7.x series installed and your
      users are suffering from unexplained application crashes, please
      turn on User-mode crash dump collection as described at:<br>
      <br>
<a class=3D"moz-txt-link-freetext" href=3D"http://msdn.microsoft.com/en-u=
s/library/windows/desktop/bb787181%28v=3Dvs.85%29.aspx">http://msdn.micro=
soft.com/en-us/library/windows/desktop/bb787181%28v=3Dvs.85%29.aspx</a><b=
r>
      <br>
      By analyzing the crash dumps we can determine if the crash is
      occurring within an OpenAFS module or not.=C2=A0 If it is, the stac=
k
      trace will provide a good clue as to where the error is.<br>
      <br>
      If the crash is not in an OpenAFS module, collecting a
      SysInternals Process Monitor trace of the last 20 million events
      (Options-&gt;History Depth) that occurred before the application
      crash.=C2=A0 Setup ProcMon to collect data and instruct the user to=

      stop data collection and save the history to a file when the
      problem occurs.=C2=A0 Examining the trace data will identify which
      calls to \\AFS were executed by the application just before the
      crash.<br>
      <br>
      <br>
    </tt>
  </body>
</html>


--------------enig62EA4D9FE26043F57EF78560
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJO5kTGAAoJENxm1CNJffh4AmYIANsyPxXVxIlpE9vVNUlyReSp
MzIrbQRUg/EOPfZ7dLDnzYsxd1e8J7uz9ndRuqjQ9GxP4uRARpknuE/enyoejCbN
qZpUbMg7bjIS6PFfJjPL2P83AkDIoDE1rJrVk2JhFqAYW8xEGcAzJF76TP2TZm2q
xKpEpmnNtseOIfiaYNlVITDr9rsZeD3+8im5z6KlJXOnX74OkKzjFaYI0Hqgz0R+
iLHWdADodQVpQESdZ9xo8iLGi38XBHMLMATxBex6h2hTBT2sDxD+04DmG4/fFIZM
jUOY7bZrzuDOh/eh5sXsiZkDcy8emo6SAss3wxdMwRN61/PRrvu9aVvi+4VuSO4=
=ZF4t
-----END PGP SIGNATURE-----

--------------enig62EA4D9FE26043F57EF78560--