From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23145 invoked by alias); 28 Mar 2003 18:21:07 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 23127 invoked from network); 28 Mar 2003 18:21:06 -0000 Received: from unknown (HELO pheriche.sun.com) (192.18.98.34) by sources.redhat.com with SMTP; 28 Mar 2003 18:21:06 -0000 Received: from ha2sca-mail1.SFBay.Sun.COM ([129.145.155.62]) by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA10997 for ; Fri, 28 Mar 2003 11:21:05 -0700 (MST) Received: from sun.com (awe173-2.AWE.Sun.COM [192.29.173.2]) by ha2sca-mail1.SFBay.Sun.COM (8.11.6+Sun/8.10.2/ENSMAIL,v2.1p1) with ESMTP id h2SIL4D23798 for ; Fri, 28 Mar 2003 10:21:04 -0800 (PST) Message-ID: <3E84922E.96F7B801@sun.com> Date: Fri, 28 Mar 2003 18:21:00 -0000 From: Chris Plummer X-Accept-Language: en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: problems with GDB on Debian 3.0 for mips Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00386.txt.bz2 I have an application I build that I can't debug with gdb on Debain 3.0 for mips (on both an SGI Indy and a Cobalt Qube 2). I've sucessfully run gdb on other large applications like xemacs. Also, if use -static when linking my app, there is no problem. This same problem can be reproduced debugging "ls". The log output is below. indy-04$ gdb ls GNU gdb 2002-04-01-cvs [snip] (gdb) run Starting program: /bin/ls (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 23611)] (no debugging symbols found)... Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 1024 (LWP 23611)] warning: Warning: GDB can't find the start of the function at 0xffffffff. [snip] 0xffffffff in ?? () (gdb) bt #0 0xffffffff in ?? () #1 0x2aacf3c8 in _dl_init () from /lib/ld.so.1 Cannot access memory at address 0x38 Any idea what the problem is? I don't subscribe to this mailing list, so please CC: me. Thanks, Chris Plummer