Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] comment cleanup
Date: Wed, 29 Dec 2010 11:16:00 -0000	[thread overview]
Message-ID: <20101229102103.GA7592@adacore.com> (raw)
In-Reply-To: <4D1A8801.8050802@vmware.com>

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

> 2010-12-28  Michael Snyder  <msnyder@vmware.com>
> 
> 	* event-loop.c: Comment clean-up.
> 	* event-loop.h: Ditto.
> 	* event-top.c: Ditto.
> 	* gdb.c: Ditto.
> 	* gdb.h: Ditto.
> 	* main.c: Ditto.
> 	* top.c: Ditto.
> 	* top.h: Ditto.	

I just noticed that gdb.c contains unadvertized code updates :-),
and this is causing the build to fail on platforms where mcheck.h
is not available (Eg. ppc-aix).

These have now been reverted with the following commit.

> Index: gdb.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/gdb.c,v
> retrieving revision 1.9
> diff -u -p -r1.9 gdb.c
> --- gdb.c	14 May 2010 20:17:37 -0000	1.9
> +++ gdb.c	29 Dec 2010 00:53:53 -0000
> @@ -20,16 +20,21 @@
>  #include "main.h"
>  #include "gdb_string.h"
>  #include "interps.h"
> +#include <mcheck.h>
>  
>  int
>  main (int argc, char **argv)
>  {
>    struct captured_main_args args;
> +  int ret;
>  
> +  mtrace ();
>    memset (&args, 0, sizeof args);
>    args.argc = argc;
>    args.argv = argv;
>    args.use_windows = 0;
>    args.interpreter_p = INTERP_CONSOLE;
> -  return gdb_main (&args);
> +  ret = gdb_main (&args);
> +  muntrace();
> +  return ret;

-- 
Joel

[-- Attachment #2: gdb.diff --]
[-- Type: text/x-diff, Size: 1297 bytes --]

commit f185a672c4ad8b37ba3b0d297b2240b004aad6a7
Author: Joel Brobecker <brobecker@adacore.com>
Date:   Wed Dec 29 14:17:12 2010 +0400

    revert previous gdb.c commit (it was not a minor comment update)
    
    gdb/ChangeLog:
    
           * gdb.c: Revert the previous change, which was probably committed
            by accident.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 43bba0c..b7be1ad 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,10 @@
 2010-12-29  Joel Brobecker  <brobecker@adacore.com>
 
+	* gdb.c: Revert the previous change, which was probably committed
+        by accident.
+
+2010-12-29  Joel Brobecker  <brobecker@adacore.com>
+
 	* ada-lang.c: Fix typo in comment.
 
 2010-12-29  Joel Brobecker  <brobecker@adacore.com>
diff --git a/gdb/gdb.c b/gdb/gdb.c
index 74f806e..bc5e6cc 100644
--- a/gdb/gdb.c
+++ b/gdb/gdb.c
@@ -20,21 +20,16 @@
 #include "main.h"
 #include "gdb_string.h"
 #include "interps.h"
-#include <mcheck.h>
 
 int
 main (int argc, char **argv)
 {
   struct captured_main_args args;
-  int ret;
 
-  mtrace ();
   memset (&args, 0, sizeof args);
   args.argc = argc;
   args.argv = argv;
   args.use_windows = 0;
   args.interpreter_p = INTERP_CONSOLE;
-  ret = gdb_main (&args);
-  muntrace();
-  return ret;
+  return gdb_main (&args);
 }

  reply	other threads:[~2010-12-29 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29  1:57 Michael Snyder
2010-12-29 11:16 ` Joel Brobecker [this message]
2010-12-29 22:30   ` Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101229102103.GA7592@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox