From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21759 invoked by alias); 6 Dec 2001 21:01:17 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 21726 invoked from network); 6 Dec 2001 21:01:12 -0000 Received: from unknown (HELO adobe.com) (192.150.11.1) by sources.redhat.com with SMTP; 6 Dec 2001 21:01:12 -0000 Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by adobe.com (1.0.0/8.11.4) with ESMTP id fB6L2H026822 for ; Thu, 6 Dec 2001 13:02:17 -0800 (PST) Received: from mailsj-v1.corp.adobe.com (mailsj-dev.corp.adobe.com [153.32.1.192]) by inner-relay-2.corp.adobe.com (8.11.4/8.11.4) with ESMTP id fB6L0D120212 for ; Thu, 6 Dec 2001 13:00:13 -0800 (PST) Received: from ZMAJEED2000 ([153.32.158.219]) by mailsj-v1.corp.adobe.com (Netscape Messaging Server 4.15 v1 Jul 11 2001 16:32:57) with SMTP id GNXX1U00.R1M; Thu, 6 Dec 2001 13:01:06 -0800 From: "Zartaj T. Majeed" To: , Subject: Letext and gdb problems on Solaris 8 Date: Thu, 06 Dec 2001 13:01:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-SW-Source: 2001-12/txt/msg00308.txt.bz2 I am running into serious problems in gdb 5.0. Here are the symptoms which occur at different places in the program. 1. Step acts like next so I cannot step into a function call. 2. gdb does not stop at breakpoints 3. bt shows only the current frame 4. bt shows frames down to an incorrectly labeled function called Letext(). Any of these makes gdb very difficult to use but encountering all of them at various points in the program makes gdb virtually unusable. I am running gdb 5.0 built with gcc 2.95.2 for Solaris 8. My program is also built with gcc 2.95.2. Trying gdb 5.1 did not help. When I ran the program it got a SIGTRAP and I could not proceed. The only clue I have is the presence of Letext in certain stack traces. There is no such symbol in my program and I know it is a symbol generated by gcc but do not know its purpose--something like __etext? Anyway bt in #4 shows something like: #6 0x... in myfunc() at myfunc_file.c:100 #7 0x... in Letext() at funccall_file.c:80 And here's a disassembly of funccall_file.c:80 which looks like some kind of stub. The actual function body at that line is over 100 lines long, so this is not its disassembly. (gdb) disas Dump of assembler code for function Letext: 0xfe06ffa8 : call 0xfe1a0794 0xfe06ffac : nop 0xfe06ffb0 : st %o0, [ %fp + -20 ] 0xfe06ffb4 : ld [ %fp + -20 ], %o0 0xfe06ffb8 : cmp %o0, 0 0xfe06ffbc : be 0xfe07015c 0xfe06ffc0 : nop 0xfe06ffc4 : clr [ %fp + -40 ] End of assembler dump. If nobody has a solution, does anyone know how I can go about determining what's going wrong with gdb or code generated by gcc? Thanks, Zartaj