2.41 Release sources

[thirdparty/binutils-gdb.git] / gdb / ppc-linux-nat.c

diff --git a/gdb/ppc-linux-nat.c b/gdb/ppc-linux-nat.c
index 42885deb45e1da2e1901fdeffaac484016b0018a..d14aba694e539d182438207f1141ea799d8dc9b4 100644 (file)
--- a/gdb/ppc-linux-nat.c
+++ b/gdb/ppc-linux-nat.c
@@ -333,7 +333,7 @@ public:
 
   /* One and only one of these three functions returns true, indicating
      whether the corresponding interface is the one we detected.  The
-     interface must already have been detected as a precontidion.  */
+     interface must already have been detected as a precondition.  */
 
   bool hwdebug_p ()
   {
@@ -454,7 +454,7 @@ private:
 
      UNAVAILABLE can indicate that the kernel doesn't support any of the
      two sets of requests or that there was an error when we tried to
-     detect wich interface is available.  */
+     detect which interface is available.  */
 
   enum debug_reg_interface
     {
@@ -1941,6 +1941,9 @@ ppc_linux_nat_target::auxv_parse (const gdb_byte **readptr,
 const struct target_desc *
 ppc_linux_nat_target::read_description ()
 {
+  if (inferior_ptid == null_ptid)
+    return this->beneath ()->read_description ();
+
   int tid = inferior_ptid.pid ();
 
   if (have_ptrace_getsetevrregs)
@@ -2126,7 +2129,7 @@ ppc_linux_nat_target::region_ok_for_hw_watchpoint (CORE_ADDR addr, int len)
          /* DAWR interface allows to watch up to 512 byte wide ranges.  */
          region_size = 512;
          /* DAWR interface allows to watch up to 512 byte wide ranges which
-            can't cross a 512 byte bondary on machines that doesn't have a
+            can't cross a 512 byte boundary on machines that don't have a
             second DAWR (P9 or less).  */
          if (!(hwdebug_info.features & PPC_DEBUG_FEATURE_DATA_BP_ARCH_31))
            region_align = 512;
@@ -2733,7 +2736,7 @@ ppc_linux_nat_target::low_forget_process (pid_t pid)
 }
 
 /* Copy the per-process state associated with the pid of PARENT to the
-   sate of CHILD_PID.  GDB expects that a forked process will have the
+   state of CHILD_PID.  GDB expects that a forked process will have the
    same hardware breakpoints and watchpoints as the parent.
 
    If we're using the HWDEBUG interface, also copy the thread debug
@@ -2880,7 +2883,7 @@ ppc_linux_nat_target::low_prepare_to_resume (struct lwp_info *lp)
                  perror_with_name (_("Error deleting hardware "
                                      "breakpoint or watchpoint"));
 
-             /* We erase the entries one at a time after successfuly
+             /* We erase the entries one at a time after successfully
                 removing the corresponding slot form the thread so that
                 if we throw an exception above in a future iteration the
                 map remains consistent.  */