This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[commit] Regenerate gdbarch.h


Not sure why, but the version currently checked in as an extraneous
trailing whitespace that showed up as a diff when I reran gdbarch.sh.

gdb/ChangeLog:

        * gdbarch.h: Regenerate.

So I'm checking the following in to fix this.

---
 gdb/ChangeLog |    4 ++++
 gdb/gdbarch.h |    2 +-
 2 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index a10d060..3b25e23 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2011-10-26  Joel Brobecker  <brobecker@adacore.com>
+
+	* gdbarch.h: Regenerate.
+
 2011-10-26  Meador Inge  <meadori@codesourcery.com>
 
 	* gdbarch.sh (function_list): Use 'pstring' when printing
diff --git a/gdb/gdbarch.h b/gdb/gdbarch.h
index d8420cc..46c5afa 100644
--- a/gdb/gdbarch.h
+++ b/gdb/gdbarch.h
@@ -592,7 +592,7 @@ extern void set_gdbarch_smash_text_address (struct gdbarch *gdbarch, gdbarch_sma
    FIXME/cagney/2001-01-18: The logic is backwards.  It should be asking if the
    target can single step.  If not, then implement single step using breakpoints.
   
-   A return value of 1 means that the software_single_step breakpoints 
+   A return value of 1 means that the software_single_step breakpoints
    were inserted; 0 means they were not. */
 
 extern int gdbarch_software_single_step_p (struct gdbarch *gdbarch);
-- 
1.7.1


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]