Description: Fix spelling-error-in-binary found by lintian
Origin: vendor
Author: Alessandro Ghedini <ghedo@debian.org>
Last-Update: 2015-09-25

--- a/coregrind/m_commandline.c
+++ b/coregrind/m_commandline.c
@@ -69,7 +69,7 @@
    fd = VG_(open)(filename, 0, VKI_S_IRUSR);
    if ( !sr_isError(fd) ) {
       Int res = VG_(fstat)( sr_Res(fd), &stat_buf );
-      // Ignore if not owned by current user or world writeable (CVE-2008-4865)
+      // Ignore if not owned by current user or world writable (CVE-2008-4865)
       if (!res && stat_buf.uid == VG_(geteuid)()
           && (!(stat_buf.mode & VKI_S_IWOTH))) {
          if ( stat_buf.size > 0 ) {
--- a/coregrind/m_gdbserver/server.c
+++ b/coregrind/m_gdbserver/server.c
@@ -254,7 +254,7 @@
 "    Valgrind internal host status/memory\n"
 "  v.translate <addr> [<traceflags>]  : debug translation of <addr> with <traceflags>\n"
 "    (default traceflags 0b00100000 : show after instrumentation)\n"
-"   An additional flag  0b100000000 allows to show gdbserver instrumentation\n");
+"   An additional flag  0b100000000 allows one to show gdbserver instrumentation\n");
       }
       break;
    case  1: /* v.set */
--- a/VEX/priv/ir_defs.c
+++ b/VEX/priv/ir_defs.c
@@ -4478,7 +4478,7 @@
    if (bb->stmts_used < 0 || bb->stmts_size < 8
        || bb->stmts_used > bb->stmts_size)
       /* this BB is so strange we can't even print it */
-      vpanic("sanityCheckIRSB: stmts array limits wierd");
+      vpanic("sanityCheckIRSB: stmts array limits weird");
 
    /* Ensure each temp has a plausible type. */
    for (i = 0; i < n_temps; i++) {
--- a/gdbserver_tests/mchelp.stdoutB.exp
+++ b/gdbserver_tests/mchelp.stdoutB.exp
@@ -80,7 +80,7 @@
     Valgrind internal host status/memory
   v.translate <addr> [<traceflags>]  : debug translation of <addr> with <traceflags>
     (default traceflags 0b00100000 : show after instrumentation)
-   An additional flag  0b100000000 allows to show gdbserver instrumentation
+   An additional flag  0b100000000 allows one to show gdbserver instrumentation
 memcheck monitor commands:
   xb <addr> [<len>]
         prints validity bits for <len> (or 1) bytes at <addr>
--- a/coregrind/m_hashtable.c
+++ b/coregrind/m_hashtable.c
@@ -298,7 +298,7 @@
    }
 
    VG_(message)(Vg_DebugMsg, 
-                "nr occurences of"
+                "nr occurrences of"
                 " chains of len N,"
                 " N-plicated keys,"
                 " N-plicated elts\n");
--- a/coregrind/m_scheduler/scheduler.c
+++ b/coregrind/m_scheduler/scheduler.c
@@ -2138,7 +2138,7 @@
       "to recompile such code, using the header files from this version of\n"
       "Valgrind, and not any previous version.\n"
       "\n"
-      "If you see this mesage in any other circumstances, it is probably\n"
+      "If you see this message in any other circumstances, it is probably\n"
       "a bug in Valgrind.  In this case, please file a bug report at\n"
       "\n"
       "   http://www.valgrind.org/support/bug_reports.html\n"