From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25249 invoked by alias); 6 Jan 2014 05:13:08 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 25228 invoked by uid 89); 6 Jan 2014 05:13:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,MSGID_MULTIPLE_AT,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 X-HELO: LGEAMRELO02.lge.com Received: from lgeamrelo02.lge.com (HELO LGEAMRELO02.lge.com) (156.147.1.126) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 06 Jan 2014 05:13:05 +0000 Received: from GNRHQ10NA10046 ( [10.186.119.205]) by LGEAMRELO02.lge.com (Symantec Brightmail Gateway) with SMTP id A9.C2.11497.F5B3AC25; Mon, 6 Jan 2014 14:13:03 +0900 (KST) From: "Honggyu Kim" To: "'Sergio Durigan Junior'" Cc: References: <1388973207-31270-1-git-send-email-hong.gyu.kim@lge.com> In-Reply-To: Subject: RE: [PATCH v2] Remove duplicated include in gdb directory Date: Mon, 06 Jan 2014 05:13:00 -0000 Message-ID: <002601cf0a9d$f9330f50$eb992df0$@gyu.kim@lge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-01/txt/msg00050.txt.bz2 Thank you for your kind feedback. I thought it's just a minor code cleanup so I didn't expect any copyright issues. I have tried to build as below. $ ./configure --prefix=`pwd`/build $ make and $ make distclean $ ./configure --prefix=`pwd`/build --enable-targets=all $ make In both cases, build were fine and gdb binary is generated without problems. However, when I tried to run gdb to debug just a simple hello world program, it fails. But I found that the current HEAD also fails by showing the following message. It seems to be very strange for me since it's not from the patch that I submitted. I have tested the same thing after checkout a tag "gdb_7_6_2-2013-12-08-release" and it worked fine. Please consider this issue separately or please correct me if I'm wrong. $ cd build/bin/ $ ./gdb ./a.out GNU gdb (GDB) 7.6.50.20140106-cvs Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./a.out...(no debugging symbols found)...done. (gdb) r Starting program: /home/hong.gyu.kim/src/gdb/binutils-gdb/build/bin/a.out *** glibc detected *** ./gdb: double free or corruption (out): 0x0000000003435860 *** ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7fc88175db96] ./gdb[0x86b8a1] ./gdb(bfd_close+0x82)[0x86be52] ... Aborted (core dumped) Hello, World -----Original Message----- From: Sergio Durigan Junior [mailto:sergiodj@redhat.com] Sent: Monday, January 06, 2014 12:47 PM To: Honggyu Kim Cc: gdb-patches@sourceware.org Subject: Re: [PATCH v2] Remove duplicated include in gdb directory On Sunday, January 05 2014, Honggyu Kim wrote: > This patch simply removes duplicated include statements in gdb directory. > If there are two duplicated include statements, this patch keeps the first > include and removes the second include. > Those are found by checkincludes.pl tool in linux kernel and double checked > manually once again if the include statements are affected by ifdef macro. Thanks for the patch, Honggyu. I believe you have tested it by building GDB with --enable-targets=all, right? It needs a ChangeLog (mechanical), and it seems to be simple enough to be committed without needing a copyright assignment (I don't see your name in the MAINTAINERS file). Other than that, let's wait for some maintainer to give the green light. BTW, if you want to get started on the process to obtain the copyright assignment, mail me offlist and I can send you the instructions. Thanks, -- Sergio