From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12138 invoked by alias); 7 Jul 2009 02:49:21 -0000 Received: (qmail 12128 invoked by uid 22791); 7 Jul 2009 02:49:20 -0000 X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_72,MEDICAL_SUBJECT,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 07 Jul 2009 02:49:13 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n672nBcK002423; Mon, 6 Jul 2009 22:49:11 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n672nAuN010554; Mon, 6 Jul 2009 22:49:10 -0400 Received: from lindt.uglyboxes.com (sebastian-int.corp.redhat.com [172.16.52.221]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n672n56u021980; Mon, 6 Jul 2009 22:49:08 -0400 Message-ID: <4A52B7A1.1080104@redhat.com> Date: Tue, 07 Jul 2009 02:49:00 -0000 From: Keith Seitz User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: daniel tian CC: insight@sourceware.org Subject: Re: About machine.md in Insight Gdb in GCC porting References: <121fadb80906291848y61466ae6yd167e6a03321d9fa@mail.gmail.com> <4A5274DB.3020705@redhat.com> <121fadb80907061904t1647fa75u7dd0710f4c8310d5@mail.gmail.com> <4A52AE7D.4030300@redhat.com> <121fadb80907061938v25fe8ad7od0ee292c19b06f4a@mail.gmail.com> In-Reply-To: <121fadb80907061938v25fe8ad7od0ee292c19b06f4a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2009-q3/txt/msg00007.txt.bz2 daniel tian wrote: > I didn't used the normal gdb command mode. I just type the Insight > command, and run it, then open my cc1 file. Change of tack: whenever you get somewhere you expect to see you .md file, open the console window and type "list". What does that say? Also, can you tell me what you do to reproduce the problem? If you give me a target triple and a test procedure, I can try to reproduce a working case here and use that to troubleshoot your scenario. Did you say some variety of arm worked? > Here is my compiling command: > > export CFLAGS='-gdwarf-2 -g3' > export LIBCFLAGS='-gdwarf-2 -g3' > export BOOT_CFLAGS='-gdwarf-2 -g3' You should not need to specify -gdwarf-2 and -g3 (that I know). On most targets, -g will default to outputting dwarf 2. Just to eliminate the possibility (and I'm not saying that specifying both will do anything wrong), try just using "-g" -- at least while we try to debug this. > I have to say the md file is not a pure C file. That should not matter as long as the compiler (and assembler, if assembly is involved) are outputting debug info. I suspect they are not, but again, I don't know anything about gcc .md files or how they are used. Keith