* exec.c (exec_file_attach): Fix comment.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index d8eb22c76bf1a86ae28d08ff1d56f0dec67b375d..093b4317389b129c4f0bff68c9dafc1744cf02cc 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2009-02-22  Doug Evans  <dje@google.com>
+
+       * exec.c (exec_file_attach): Fix comment.
+
 2009-02-22  Pedro Alves  <pedro@codesourcery.com>
 
        Silence a few -Wmissing-prototypes warnings.

diff --git a/gdb/exec.c b/gdb/exec.c
index 8d8c1dfe5a4bc630ced9b7f6e97784c166bcf816..a9a53ce631f3b61fc38543e59483b3c50f627a74 100644 (file)
--- a/gdb/exec.c
+++ b/gdb/exec.c
@@ -158,7 +158,7 @@ exec_file_clear (int from_tty)
     printf_unfiltered (_("No executable file now.\n"));
 }
 
-/*  Process the first arg in ARGS as the new exec file.
+/* Set FILENAME as the new exec file.
 
    This function is intended to be behave essentially the same
    as exec_file_command, except that the latter will detect when
@@ -173,9 +173,7 @@ exec_file_clear (int from_tty)
    given a pid but not a exec pathname, and the attach command could
    figure out the pathname from the pid.  (In this case, we shouldn't
    ask the user whether the current target should be shut down --
-   we're supplying the exec pathname late for good reason.)
-   
-   ARGS is assumed to be the filename. */
+   we're supplying the exec pathname late for good reason.)  */
 
 void
 exec_file_attach (char *filename, int from_tty)