[NFC] Remove ASCII lines from comments

A lot of comments in LLDB are surrounded by an ASCII line to delimit the
begging and end of the comment.

Its use is not really consistent across the code base, sometimes the
lines are longer, sometimes they are shorter and sometimes they are
omitted. Furthermore, it looks kind of weird with the 80 column limit,
where the comment actually extends past the line, but not by much.
Furthermore, when /// is used for Doxygen comments, it looks
particularly odd. And when // is used, it incorrectly gives the
impression that it's actually a Doxygen comment.

I assume these lines were added to improve distinguishing between
comments and code. However, given that todays editors and IDEs do a
great job at highlighting comments, I think it's worth to drop this for
the sake of consistency. The alternative is fixing all the
inconsistencies, which would create a lot more churn.

Differential revision: https://reviews.llvm.org/D60508

llvm-svn: 358135

1 files changed, 0 insertions, 8 deletions

diff --git a/lldb/tools/debugserver/source/libdebugserver.cpp b/lldb/tools/debugserver/source/libdebugserver.cpp
index 450ce41de25..e545caf5ae8 100644
--- a/lldb/tools/debugserver/source/libdebugserver.cpp
+++ b/lldb/tools/debugserver/source/libdebugserver.cpp
@@ -26,9 +26,7 @@
 #include "RNBSocket.h"
 #include "SysSignal.h"
 
-//----------------------------------------------------------------------
 // Run loop modes which determine which run loop function will be called
-//----------------------------------------------------------------------
 typedef enum {
   eRNBRunLoopModeInvalid = 0,
   eRNBRunLoopModeGetStartModeFromRemoteProtocol,
@@ -36,9 +34,7 @@ typedef enum {
   eRNBRunLoopModeExit
 } RNBRunLoopMode;
 
-//----------------------------------------------------------------------
 // Global Variables
-//----------------------------------------------------------------------
 RNBRemoteSP g_remoteSP;
 int g_disable_aslr = 0;
 int g_isatty = 0;
@@ -60,12 +56,10 @@ int g_isatty = 0;
     }                                                                          \
   } while (0)
 
-//----------------------------------------------------------------------
 // Get our program path and arguments from the remote connection.
 // We will need to start up the remote connection without a PID, get the
 // arguments, wait for the new process to finish launching and hit its
 // entry point,  and then return the run loop mode that should come next.
-//----------------------------------------------------------------------
 RNBRunLoopMode RNBRunLoopGetStartModeFromRemote(RNBRemoteSP &remoteSP) {
   std::string packet;
 
@@ -125,11 +119,9 @@ RNBRunLoopMode RNBRunLoopGetStartModeFromRemote(RNBRemoteSP &remoteSP) {
   return eRNBRunLoopModeExit;
 }
 
-//----------------------------------------------------------------------
 // Watch for signals:
 // SIGINT: so we can halt our inferior. (disabled for now)
 // SIGPIPE: in case our child process dies
-//----------------------------------------------------------------------
 nub_process_t g_pid;
 int g_sigpipe_received = 0;
 void signal_handler(int signo) {