* dwarf2read.c (create_dwo_in_dwp): Tweak comment.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index cbc3e7cbfdd09ab57540b34a2aaca65cac8076cd..5f9ef4db5ed3ac18f9c830ae39b19c5b2554d2cf 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,7 @@
 2012-12-10  Doug Evans  <dje@google.com>
 
+       * dwarf2read.c (create_dwo_in_dwp): Tweak comment.
+
        * symtab.c (find_pc_sect_symtab): Add comment.
 
 2012-12-10  Tom Tromey  <tromey@redhat.com>

diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index 2168c69ef2d51b5f2a552d4ce79a7dc25ab2ea0e..7a1bbc5bf7ac3a2101b9538d831ca9cf90d875cf 100644 (file)
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -8594,8 +8594,8 @@ create_dwo_in_dwp (struct dwp_file *dwp_file,
      have dwo_unit "live" in that.  At least for now.
 
      The DWP file can be made up of a random collection of CUs and TUs.
-     However, for each CU + set of TUs that came from the same original
-     DWO file, we want combine them back into a virtual DWO file to save space
+     However, for each CU + set of TUs that came from the same original DWO
+     file, we want to combine them back into a virtual DWO file to save space
      (fewer struct dwo_file objects to allocated).  Remember that for really
      large apps there can be on the order of 8K CUs and 200K TUs, or more.  */