aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Pluzhnikov <ppluzhnikov@google.com>2011-08-05 15:17:23 +0000
committerPaul Pluzhnikov <ppluzhnikov@google.com>2011-08-05 15:17:23 +0000
commitd989b283238d3aeffa567106ec2d75d4cdf1827b (patch)
treec2a79e151ca1f2fd7b249cdabc79a4e23bd48c07
parent6a1b16642bd239e1eb15f644e367526590316540 (diff)
downloadgdb-d989b283238d3aeffa567106ec2d75d4cdf1827b.zip
gdb-d989b283238d3aeffa567106ec2d75d4cdf1827b.tar.gz
gdb-d989b283238d3aeffa567106ec2d75d4cdf1827b.tar.bz2
Clean up trailing white space
-rw-r--r--gdb/solib-svr4.c12
1 files changed, 6 insertions, 6 deletions
diff --git a/gdb/solib-svr4.c b/gdb/solib-svr4.c
index d92a83c..dffc6213 100644
--- a/gdb/solib-svr4.c
+++ b/gdb/solib-svr4.c
@@ -116,8 +116,8 @@ svr4_same_1 (const char *gdb_so_name, const char *inferior_so_name)
return 1;
/* On Solaris, when starting inferior we think that dynamic linker is
- /usr/lib/ld.so.1, but later on, the table of loaded shared libraries
- contains /lib/ld.so.1. Sometimes one file is a link to another, but
+ /usr/lib/ld.so.1, but later on, the table of loaded shared libraries
+ contains /lib/ld.so.1. Sometimes one file is a link to another, but
sometimes they have identical content, but are not linked to each
other. We don't restrict this check for Solaris, but the chances
of running into this situation elsewhere are very low. */
@@ -1662,7 +1662,7 @@ enable_break (struct svr4_info *info, int from_tty)
DESCRIPTION
Once the symbols from a shared object have been loaded in the usual
- way, we are called to do any system specific symbol handling that
+ way, we are called to do any system specific symbol handling that
is needed.
For SunOS4, this consisted of grunging around in the dynamic
@@ -1737,7 +1737,7 @@ read_program_headers_from_bfd (bfd *abfd, int *phdrs_size)
So, to summarize, relocations are necessary when the start address obtained
from the executable is different from the address in auxv AT_ENTRY entry.
-
+
[ The astute reader will note that we also test to make sure that
the executable in question has the DYNAMIC flag set. It is my
opinion that this test is unnecessary (undesirable even). It
@@ -2359,7 +2359,7 @@ svr4_have_link_map_offsets (void)
/* Fetch (and possibly build) an appropriate `struct link_map_offsets'
for an ILP32 SVR4 system. */
-
+
struct link_map_offsets *
svr4_ilp32_fetch_link_map_offsets (void)
{
@@ -2390,7 +2390,7 @@ svr4_ilp32_fetch_link_map_offsets (void)
/* Fetch (and possibly build) an appropriate `struct link_map_offsets'
for an LP64 SVR4 system. */
-
+
struct link_map_offsets *
svr4_lp64_fetch_link_map_offsets (void)
{